forked from nedap/archie
-
Notifications
You must be signed in to change notification settings - Fork 27
Releasing & deploying
Mattijs Kuhlmann edited this page Jul 4, 2025
·
8 revisions
Archie is published to the Central Repository. For setup, follow the steps in http://central.sonatype.org/pages/gradle.html.
Take the following steps to deploy and release Archie to version x.x.x:
- In the build.gradle file, update the version of the project
- In the README, also update the version anywhere that it is used
- Commit these two files with the message "Update version to x.x.x"
- Add a tag to this version
git tag vx.x.xgit push --tags
- Push the changes
git push
- Go to Github Releases and add release notes for the newly added tag
-
Make sure you have a Maven Central account with the correct rights (documentation)
-
Make sure you have GPG setup with a private key recognized by Maven Central (documentation)
-
Make sure you have added your signing keys and your maven central token id and secret added to your gradle.properties file. It should look something like this:
signing.keyId= signing.gnupg.executable=gpg signing.gnupg.keyName= signing.gnupg.passphrase= centralTokenUsername= centralTokenPassword=
- Running the following Gradle command will directly publish, close and release the project to Maven Central:
./gradlew clean build publishToSonatype closeAndReleaseSonatypeStagingRepository- The status should be visible on this page: https://central.sonatype.com/publishing/deployments