-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Home
Welcome to the jjwt wiki!
-
Ensure all
@since JJWT_RELEASE_VERSION
references are changed to the version you are about to release. Commit/push these changes. -
Ensure all version references (dependency declarations, etc) in
README.md
have been replaced with the version you are about to release. Commit/push this change. -
Ensure the correct
~/.m2/settings.xml
are enabled (not using a company private repo) and thesonatype-oss-release
andstormpath-signature
profiles are enabled. -
Ensure you have the Zulu JDK 7 installation here: https://www.azul.com/downloads/?version=java-7-lts&os=macos&architecture=x86-64-bit&package=jdk
-
Ensure
java -version
equals this Zulu JDK 7 -
Ensure MAVEN_OPTS is set properly:
export MAVEN_OPTS="-Dhttps.protocols=TLSv1.2 -Xmx512m -XX:MaxPermSize=128m"
-
Run the release build:
mvn clean mvn release:clean mvn release:prepare # Choose a version number. # Choose an SCM release tag. This should be *just* the version number: 0.5, not jjwt-0.5 # Choose the new development version. If releasing 0.5, this would be 0.6-SNAPSHOT mvn release:perform -Possrh
-
In the
master
branch (and in theMaj.min.x
branch if you are cutting a patch release), change the root pom.xmljjwt.previousVersion
property value to equal the version just released. Commit and push these changes. -
Log in to the Sonatype OSS admin console
-
On the menu on the left, click the
Staging Repositories
link. On the resulting list, findiojsonwebtoken-
### (usually at the bottom of the list). Check the checkbox for that item. -
Click the
Close
button at the top of the list. Add in a quick note (e.g. 'Closing for the 0.5 release') and clickConfirm
. -
Wait a minute or so and click the
Refresh
button at the top of the list. TheRelease
button should now be enabled. ClickRelease
and enter in a quick note (e.g. 'Releasing 0.5'). Ensure theAutomatically Drop
option IS checked (you want this). ClickConfirm
. -
Logout.
That's it! The release should show up in Maven Central in 15 to 30 minutes.