...
If the snapshot artifacts do not exist, you can deploy them to Sonatype with the following command:
| Code Block | ||
|---|---|---|
| ||
mvnmvn -DaltDeploymentRepository=sonatype-nexus-snapshots::default::https://oss.sonatype.org/content/repositories/snapshots/ deploy -DskipTests |
Build resources
These build scripts may be of use for building the set of release candidate modules.
Update online resources
If any online resources have been modified or added to during the release, these must be updated.
...
Push Release Branch to Maintenance
The release branch has changes made since code freeze. It also contains the update to the version numbers for future development.
...
Ensure that your commit history matches the release branch's commit history, except for the two additional commits.
- Changing from SNAPSHOT version to release version. Something like [maven-release-plugin] prepare release $REPO-$CURR
- Changing from release version to next development version. Something like [maven-release-plugin] prepare for next development iteration
...
If this appears correct, you can push your release branch on to the maintenance branch.
...