Skip to content

RELEASE.md

Latest commit

 

History

History
41 lines (27 loc) · 1.21 KB

RELEASE.md

File metadata and controls

41 lines (27 loc) · 1.21 KB
Raw

Releasing Pi4J

Create a new release

To release pi4j use the following:

MVN_PROFILES=-P\!default ./autoReleaseBranch minor develop release/<version>

this merges the develop branch into release/<version>, increments the current tag on the release/<version> branch and then builds it locally. It uses mvn versions:set to set the version, and after the version is set, does a test build to make sure all dependencies are really there.

The tag is signed by the configured git signing key. The key used can be checked with:

git config --get user.signingkey

Deploy to Maven central

To deploy to maven, use the following commands:

MVN_PROFILES=-P\!default ./deployToMavenCentral.sh <version>

This checks out the given tag and used the deploy profile to build and push the artifacts to maven central.

Now don't forget to publish the release on Maven central: https://central.sonatype.com/publishing/deployments

Update snapshot version

To create a new snapshot version on develop branch, use the following two commands:

mvn versions:set -DgenerateBackupPoms=false -DnewVersion="${newVersion}"
mvn clean install

Then commit and push the changed pom.xml files.