-
Notifications
You must be signed in to change notification settings - Fork 532
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
86c0d62
commit 05f551a
Showing
1 changed file
with
31 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Java Wrapper Release Process | ||
|
||
* code: https://github.com/watson-developer-cloud/java-wrapper | ||
* maven: http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22java-wrapper%22 | ||
|
||
## Guide to uploading artifacts to the Central Repository | ||
|
||
We use sonatype as repository manager, it's used as the input channel for the Central Repository running the Sonatype Open Source Repository Hosting OSSRH service. | ||
|
||
### Prerequisites | ||
If you are not familiar with sonatype and/or the maven release process please read the following material: | ||
* Sonatype: http://central.sonatype.org/pages/apache-maven.html | ||
* Releasing artifacts to Sonatype: http://kirang89.github.io/blog/2013/01/20/uploading-your-jar-to-maven-central/ | ||
* Install GPG and create a public key. More info: http://blog.sonatype.com/2010/01/how-to-generate-pgp-signatures-with-maven/#.VUL_DtNViko | ||
|
||
|
||
### Release steps | ||
|
||
1. Make sure that `pom.xml` and `build.gradle` have the same version number. In the `pom.xml` file the version should ends with -SNAPSHOT | ||
|
||
2. With the SCM connection configured correctly you can perform a release deployment to OSSRH (Staging) with: | ||
|
||
`mvn release:clean release:prepare` | ||
|
||
You will have to answer prompts for versions and tags. That will tag and commit a new version into your repository automatically. | ||
|
||
3. Deploy to maven central: | ||
|
||
`mvn release:perform` | ||
|
||
This execution will deploy to OSSRH and release to the Central Repository in one go. |