- increment version in
pom.xml - compile and package the project:
mvn clean package source:jar- import gpg key to sign files
gpg --import sonatype_emartech_gpg_private.key- sign files
- key passphrase: https://secret.emarsys.net/cred/detail/2542/
cp pom.xml target
cd target
gpg -ab --default-key 41EBF74D9F93DA29 pom.xml
gpg -ab --default-key 41EBF74D9F93DA29 escher-${NEW_VERSION_NUMBER}.jar
gpg -ab --default-key 41EBF74D9F93DA29 escher-${NEW_VERSION_NUMBER}-javadoc.jar
gpg -ab --default-key 41EBF74D9F93DA29 escher-${NEW_VERSION_NUMBER}-sources.jar- bundle lib
jar -cvf bundle.jar pom.xml pom.xml.asc escher-${NEW_VERSION_NUMBER}.jar escher-${NEW_VERSION_NUMBER}.jar.asc escher-${NEW_VERSION_NUMBER}-javadoc.jar escher-${NEW_VERSION_NUMBER}-javadoc.jar.asc escher-${NEW_VERSION_NUMBER}-sources.jar escher-${NEW_VERSION_NUMBER}-sources.jar.asc- log in to https://oss.sonatype.org/, creds: https://secret.emarsys.net/cred/detail/2473/
- upload bundle.jar at https://oss.sonatype.org/#staging-upload, upload mode -> Artifact Bundle
- go to https://oss.sonatype.org/#stagingRepositories
- wait a bit until the release button become available
- press release on the staging repo created for the bundle
- wait until is it automatically deployed to maven central (it can take up to 2 hours to appear in MC)