Skip to content

Commit 05f551a

Browse files
added release information
1 parent 86c0d62 commit 05f551a

File tree

1 file changed

+31
-0
lines changed

1 file changed

+31
-0
lines changed

RELEASE.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Java Wrapper Release Process
2+
3+
* code: https://github.com/watson-developer-cloud/java-wrapper
4+
* maven: http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22java-wrapper%22
5+
6+
## Guide to uploading artifacts to the Central Repository
7+
8+
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.
9+
10+
### Prerequisites
11+
If you are not familiar with sonatype and/or the maven release process please read the following material:
12+
* Sonatype: http://central.sonatype.org/pages/apache-maven.html
13+
* Releasing artifacts to Sonatype: http://kirang89.github.io/blog/2013/01/20/uploading-your-jar-to-maven-central/
14+
* Install GPG and create a public key. More info: http://blog.sonatype.com/2010/01/how-to-generate-pgp-signatures-with-maven/#.VUL_DtNViko
15+
16+
17+
### Release steps
18+
19+
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
20+
21+
2. With the SCM connection configured correctly you can perform a release deployment to OSSRH (Staging) with:
22+
23+
`mvn release:clean release:prepare`
24+
25+
You will have to answer prompts for versions and tags. That will tag and commit a new version into your repository automatically.
26+
27+
3. Deploy to maven central:
28+
29+
`mvn release:perform`
30+
31+
This execution will deploy to OSSRH and release to the Central Repository in one go.

0 commit comments

Comments
 (0)