-
Notifications
You must be signed in to change notification settings - Fork 32
Release to Maven Central
Follow this tutorial.
-
No route to host
: probably an IPv6 issue. List available servers withgpg-connect-agent --dirmngr 'keyserver --hosttable'
and pick one with IPv4, or use ipv4.pool.sks-keyservers.net. -
Inappropriate ioctl for device
:GPG_TTY=$(tty); export GPG_TTY
does the trick (source https://github.com/pstadler/keybase-gpg-github/issues/11).
Make sure you created an SSH key and added it to your Github account (see https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/).
Make sure your OSSRH JIRA account is properly set up in ~/.m2/settings.xml
(see https://github.com/liquigraph/liquigraph/blob/master/deploy-settings.xml).
Generate the maven plugin site (see the Zsh script in liquigraph-maven-plugin
).
This script assumes the project is at version XXX-SNAPSHOT and XXX is about to be released.
Once executed, update the Github pages repository (liquigraph.github.io
) with liquigraph-maven-plugin/target/site
(this last step can be done after the release if you move the site folder into some location outside the project tree).
Just run:
-
mvn release:prepare -Prelease-sign-artifacts
(SCM label isliquigraph-$VERSION
, which should be automatically set) and mvn release:perform -Prelease-sign-artifacts
- then go to https://oss.sonatype.org/ and validate the release:
- go to staging repositories and locate Liquigraph
- verify that all the artifacts are present and close the release
- then release it!
- Edit the release notes (check previous examples for some kind of consistency)
- Update the online documentation
- do not forget to update the maven plugin pages
- if the schema has changed, do not forget to add the new version and update the examples
- Update the Homebrew recipes (both in https://github.com/Homebrew/homebrew-core and https://github.com/liquigraph/homebrew-liquigraph)