Changing release instructions.

* There is currently a bug in Gradle release plugin plugin that requires the keys to be passed as parameters instead of gradle.properties. GRADLE-3281
tomasbjerre · Nov 16, 2015 · 69146dc · 69146dc
1 parent e10b8a0
commit 69146dc
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/README.md b/README.md
@@ -81,4 +81,4 @@ And then to generate CHANGELOG.md, just run `gradle gitChangelog`.
 
 To build the code you need to run `build.sh` in root of repo. You may also have a look at `.travis.yml`.
 
-To do a release you need to do `./gradlew release` and release the artifact from [staging](https://oss.sonatype.org/#stagingRepositories). More information [here](http://central.sonatype.org/pages/releasing-the-deployment.html).
+To do a release you need to do `./gradlew release -Dgradle.publish.key=... -Dgradle.publish.secret=...` and release the artifact from [staging](https://oss.sonatype.org/#stagingRepositories). More information [here](http://central.sonatype.org/pages/releasing-the-deployment.html).