https://github.com/victornoel/smac-poms
Parent poms to deploy IRIT SMAC Team's artefacts on Maven Central
https://github.com/victornoel/smac-poms
Last synced: 7 months ago
JSON representation
Parent poms to deploy IRIT SMAC Team's artefacts on Maven Central
- Host: GitHub
- URL: https://github.com/victornoel/smac-poms
- Owner: victornoel
- Created: 2015-07-25T16:13:27.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2021-03-13T11:38:44.000Z (over 4 years ago)
- Last Synced: 2025-02-17T05:58:37.025Z (9 months ago)
- Homepage:
- Size: 11.7 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README
Awesome Lists containing this project
README
Do not use parent and parent-may, they are only kept here for reference.
parent-central is for artefact to be deployed on maven central under a sub-groupId of fr.irit.smac
To release a maven artifact (using parent-may as a parent to OSS Sonatype) of version 1.2.1 for example, follow these instructions:
Prerequisites:
1) a GnuPG signing key (until now, I used mine: 88E33689 but any can be used)
2) a OSS Sonatype account associated to the groupId fr.irit.smac (until now, I used mine: victor.noel, I am the only one that can add other people via https://issues.sonatype.org/browse/OSSRH-12012).
It should be configured as a Maven server in the settings.xml file as explained on this page: http://central.sonatype.org/pages/apache-maven.html#distribution-management-and-authentication
3) Encouraged: git must be configured with an @irit.fr email author and if possible, the same as the email used in the GnuPG signature key
1) Prepare for release by setting the version (from the parent project, not aggregator!!!)
$ mvn versions:set -DnewVersion=1.2.1
2) Compile and deploy to an OSS Sonatype staging directory
$ mvn -P release -Dgpg.keyname=88E33689 clean deploy
3) Commit and tag it
$ git commit -am "v1.2.1 release"
$ git tag -as -u 88E33689 v1.2.1 -m "v1.2.1 release"
4) Prepare for next version
$ mvn versions:set -DnewVersion=1.2.2-SNAPSHOT
5) Commit
$ git commit -am "increment to 1.2.2 development version"
6) Release the new version on Maven central and githut
$ git push --follow-tags
a) Via the OSS Sonatype Nexus UI:
go to https://oss.sonatype.org/#stagingRepositories, login and release the staging repository
b) Via command line:
$ mvn nexus-staging:release