honeymoose
/
jjwt
mirror of https://github.com/jwtk/jjwt.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updating release steps for accuracy based on current build edits

Les Hazlewood 2022-04-25 16:58:01 -04:00
parent 9d3b6c88b2
commit 6b215108c8
1 changed files with 48 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
Home.md

@ -6,11 +6,54 @@ Welcome to the jjwt wiki!
1. 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.
1. Ensure the correct `~/.m2/settings.xml` are enabled (not using a company private repo) and the `sonatype-oss-release` and `stormpath-signature` profiles are enabled.
1. Ensure the correct `~/.m2/settings.xml` are enabled (not using a company private repo) and you have **both** the `ossrh` _profile_
**and** `ossrh` _server_ enabled as follows:
```xml
<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>
<profile>
<id>ossrh</id>
<properties>
<!--
All artifacts uploaded to Nexus/OSSRH for release must be verified via digital signatures,
so configure gpg (or gpg2) for signing with a gpg key. More information can be found here:
https://central.sonatype.org/publish/requirements/gpg/
-->
<gpg.executable>gpg</gpg.executable> <!-- or gpg2 if that's what you have installed -->
<gpg.keyname>YOUR_GPG_KEY_ID</gpg.keyname>
<gpg.passphrase>YOUR_GPG_KEY_PASSPHRASE</gpg.passphrase>
</properties>
</profile>
<!-- ... any other profiles you may have for your own needs ... -->
</profiles>
<servers>
<server>
<id>ossrh</id>
<!--
This is the same username and password you use to login to both
https://issues.sonatype.org and https://oss.sonatype.org.
-->
<username>YOUR_OSSRH_USERNAME</username>
<password>YOUR_OSSRH_PASSWORD</password>
</server>
<!-- ... any other servers you may have for your own needs ... -->
</servers>
1. 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
</settings>
```
1. Ensure `java -version` equals this Zulu JDK 7
1. Ensure you have the [Zulu JDK 7](https://www.azul.com/downloads/?version=java-7-lts&package=jdk) installed.
1. Ensure `java -version` equals this Zulu JDK 7, e.g. the output looks something like this:
```bash
openjdk version "1.7.0_342"
OpenJDK Runtime Environment (Zulu 7.54.0.13-CA-macosx) (build 1.7.0_342-b01)
OpenJDK 64-Bit Server VM (Zulu 7.54.0.13-CA-macosx) (build 24.342-b01, mixed mode)
```
1. Ensure MAVEN_OPTS is set properly:
```bash
@ -26,12 +69,12 @@ Welcome to the jjwt wiki!
# 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
mvn release:perform
```
1. In the `master` branch (and in the `Maj.min.x` branch if you are cutting a patch release), change the root pom.xml `jjwt.previousVersion` property value to equal the version just released. Commit and push these changes.
1. Log in to the [Sonatype OSS admin console](https://oss.sonatype.org)
1. Log in to the [Sonatype OSSRH admin console](https://oss.sonatype.org)
1. On the menu on the left, click the `Staging Repositories` link. On the resulting list, find `iojsonwebtoken-`### (usually at the bottom of the list). Check the checkbox for that item.