Community
Participate
Working Groups
Currently, process scripts (like update_dependency.rb and ripplor.rb) together with their support scripts (e.g. lib/repository.rb) are stored in web-server/scripts. Their content varies depending upon the branch of the web-server repository fetched. Since the scripts apply to the repositories as a whole it makes a lot more sense to put them in a separate repository and have this separately versioned. The variations for managing different versions of the repositories they manipulate should be factored into separate configuration objects. It would be possible to have configurations for various 'product-sets' so that, for example, the standard (common) releaselor can be run against a versioned-product-set to release, say, 2.2 of virgo web-server. The releaselor command can take a product-set parameter to decide which one we are releasing. The present arrangement forces us to do dual (and potentially triple, or quadruple) maintenance. The classic way to prevent this is to factor and make common. This enhancement suggests we do this properly.
All the scripts now live in the new Packaging repo. While not all the issues below have been addressed it is possible to do so and separate issues have been raised for them. https://bugs.eclipse.org/bugs/show_bug.cgi?id=387626 https://bugs.eclipse.org/bugs/show_bug.cgi?id=387621
