Project

General

Profile

Bug #5127

Make a good way to publish a suite without changing a bunch of modules.txt files

Added by Sean Riddle about 9 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
build system
Target version:
Start date:
08/04/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5127

Description

As shown in the publishing instructions page on the wiki (https://kepler-project.org/developers/teams/build/documentation/publishing-steps/), you have to manually modify the modules.txt file from each module branch that you are publishing. It would be nice if this process were streamlined.

History

#1 Updated by David Welker over 8 years ago

It is no longer necessary to modify modules.txt as part of the release process as long as you want automatic upgrades for patches, which will typically be the case. If you do not want modules.txt to be change automatically for you, you can just set -Dreference-patches=false and the modules.txt you specify will not be modified.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5127

Also available in: Atom PDF