| Spring Framework/Spring Security EBR Release Process [message #1095900] |
Tue, 27 August 2013 13:36 |
 Greg Turnquist
Messages: 1
Registered: August 2013 |
Junior Member |
|
|
CAVEAT: These notes are provided only for clues as to how SpringSource used to update Spring Framework and Spring Security bundles in the SpringSource Enterprise Bundle Repository. Do not expect the following process or scripts to work identically in the Eclipse Bundle Recipes project.
Spring Framework OSGi release process:
------------------------------------------------------------
1. After building a given label of the Spring Framework, you then need to run the OSGi staging script:
$ ./copy_springframework_into_artifacts.bash /path/to/spring <old_tag> <new_tag>
This script creates a new folder named <new_tag>, copies all the template/license files from <old_tag>, edits them to replace <old_tag> with <new_tag>, and then copies the built jars from /path/to/spring into <new_tag>. Thus, it is assumed that the current working directory where the script is run is where one can see all the version folders. Also, Spring Framework labels are prefixed with a "v", like "v3.2.4.RELEASE". There is no requirement to adopt this convention for the <old_tag> and <new_tag>.
2. The script will print out a set of instructions, directing you to run a diff report on Spring's build file. This is used to spot changes in 3rd party library versions so you know what edits to make to which template files.
3. Extra manual steps are required if <new_tag> is of a different release type than <old_tag>. For example, if <old_tag> was a release, but <new_tag> is a milestone, you probably need to edit all the template files so that the published bundles are uploaded to
the milestone bucket (assuming that's your intention).
4. With everything set up, you can now publish! Spring's EBR used a combination of ant clean publish-test && ant clean publish -propertyfile /path/to/s3.properties, but this should probably be replaced by the steps used to properly publish to the target destination of the Eclipse Bundle Repository.
Spring Security OSGi release process:
------------------------------------------------------------
1. After building a given label of Spring Security, you then need to run the OSGi staging script:
$ ./copy_springsecurity_into_artifacts.bash /path/to/springsecurity <old_tag> <new_tag>
This script creates a new folder named <new_tag>, copies all the template/license files from <old_tag>, edits them to replace <old_tag> with <new_tag>, and then copies the built jars from /path/to/springsecurity into <new_tag>. Thus, it is assumed that the current working directory where the script is run is where one can see all the version folders.
2. The script will print out a set of instructions, directing you to run a diff report on Spring Security's build file. This is used to spot changes in 3rd party library versions so you know what edits to make to which template files.
3. Extra manual steps are required if <new_tag> is of a different release type than <old_tag>. For example, if <old_tag> was a release, but <new_tag> is a milestone, you probably need to edit all the template files so that the published bundles are uploaded to the milestone bucket (assuming that's your intention).
4. With everything set up, you can now publish! Spring's EBR used a combination of ant clean publish-test && ant clean publish -propertyfile /path/to/s3.properties, but this should probably be replaced by the steps used to properly publish to the target destination of the Eclipse Bundle Repository.
|
|
|
Powered by
FUDForum. Page generated in 0.01439 seconds
] 
Search
Help
Register
Login
Home
