...
- fcrepo-build-tools: if schedule for a release, must be handled first since it's version number is present in the other modules
- fcrepo4: the main project, always part of a release, takes the vast majority of the time (also push gh-pages)
- fcrepo-message-consumer (also push gh-pages)
- fcrepo-module-auth-rbacl (also push gh-pages)
- fcrepo-module-auth-xacml (also push gh-pages)
- fcrepo4-client (also push gh-pages)
- fcrepo-camel (push to sonatype, not gh-pages)
- ----
- fcrepo-sample-dataset (no push to sonatype, just version bump)
- fcrepo-webapp-plus (ditto re:no push to sonatype)
- fcrepo4-release-tests (ditto)
- fcrepo4-oaiprovider (ditto)fcrepo-camel (ditto)
- ontology (ditto)
Merge the release candidate branch into master (if any commits were made)
...
| No Format |
|---|
mvn checkout -b local-release mvn release:clean mvn release:prepare -DdryRun -DreleaseVersion=X.X.X -DdevelopmentVersion=X.X.Y-SNAPSHOT -DautoVersionSubmodules=true -DpushChanges=false mvn release:clean && Note: If there are javadoc failures, use the following, then file a JIRA ticket for the next development cycle mvn release:prepare -DreleaseVersion=X.X.X -DdevelopmentVersion=X.X.Y-SNAPSHOT -DautoVersionSubmodules=true -DpushChanges=false -Darguments="-Dmaven.javadoc.failOnError=false" |
Review the local commits for correctness (`git diff HEAD~1`, and `git diff HEAD~2`)
- Remove/or move local Maven repository
...