-
Notifications
You must be signed in to change notification settings - Fork 24
HOWTO: Performing a Release for MSL's Java Client
Daniel Koo edited this page Aug 15, 2014
·
3 revisions
Execute the following steps to perform a release:
Prereq: Add sonatype server information to your maven settings.xml
<servers>
<server>
<id>sonatype-nexus-snapshots</id>
<username>###USERNAME###</username>
<password>###PASSWORD###</password>
</server>
<server>
<id>sonatype-nexus-staging</id>
<username>###USERNAME###</username>
<password>###PASSWORD###</password>
</server>
</servers>
- In master, modify in msl-client-java/pom.xml with the release version (e.g. if current is 1.0.0-SNAPSHOT, change to 1.0.0)
- In master, modify inside of in msl-client-java/pom.xml to the desired tag name (e.g. msl-client-java-1.0.0)
- Push the change into master
- Checkout master
- Create a tag using the name set in step 2 (e.g. git tag -a msl-client-java-1.0.0 -m 'MSL Client Java Release 1.0.0' and then git push --tags)
- Have msl-sample-app running (to be used for executing unit tests)
- Run mvn clean deploy -Prelease-sign-artifacts -f msl-client/java/pom.xml -Dgpg.passphrase=###PASSPHRASE###
- Login at https://oss.sonatype.org/
- Click 'Staging Repositories'
- Search for 'finra'
- Choose 'org.finra-###' and click 'Close'
- Enter release description in the popup and submit
- Refresh
- Choose 'org.finra-###' and click 'Release'
- Enter release description in the popup and submit
- You should have received 2 e-mail notifications
- Staging Completed
- Promotion Completed
- Active sync to Maven Central Repo should already be activated so you will see the artifact within the next 24 hours.
- If everything's well, in master, modify in msl-client-java/pom.xml with the next development version (e.g. if current is 1.0.0, change to 1.0.1-SNAPSHOT)
- In master, modify inside of in msl-client-java/pom.xml to HEAD
- Push the change into master