...
| Code Block | ||
|---|---|---|
| ||
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<id>ossrh</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<gpg.keyname>YourKeyName</gpg.keyname>
<gpg.passphrase>YourKeyPassphrase</gpg.passphrase>
<gpg.defaultKeyring>false</gpg.defaultKeyring>
<gpg.useagent>true</gpg.useagent>
<gpg.lockmode>never</gpg.lockmode>
<gpg.homedir>YourGPGDir</gpg.homedir>
<gpg.publicKeyring>YourGPGDir/pubring.gpg</gpg.publicKeyring>
<gpg.secretKeyring>YourGPGDir/secring.gpg</gpg.secretKeyring>
</properties>
</profiles>
<servers>
<!--Login info for Sonatype SnapShot repository-->
<server>
<id>ossrh</id>
<username>YourSonatypeUsername</username>
<password>YourSonatypePassword</password>
</server>
<server>
<id>sonatype-nexus-snapshots</id>
<username>YourSonatypeUsername</username>
<password>YourSonatypePassword</password>
</server>
<server>
<id>github</id>
<username>your-github-id</username>
<password>your-github-pwd</password>
</server>
</servers>
</settings> |
...
If the snapshot artifacts do not exist, you can deploy them to Sonatype with the following command: (Note: "sonatype-nexus-snapshots" is the server name used in the maven settings.xml file)
| Code Block |
|---|
mvn -DaltDeploymentRepository=sonatype-nexus-snapshots::default::https://oss.sonatype.org/content/repositories/snapshots/ deploy -DskipTests |
...
Push Release Branch to develop and 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.
...