From cfc6182397016dbaff815bc95dedf2177a5593ae Mon Sep 17 00:00:00 2001 From: Roger Hu Date: Mon, 1 May 2017 11:33:01 -0700 Subject: [PATCH] Update README.md More info about maven-publish limitations --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index d82e13d..c1dfdfe 100644 --- a/README.md +++ b/README.md @@ -126,7 +126,11 @@ The plugin supports three methods to create groups of artifacts: Configurations, * Applying the *maven-publish* plugin is required when using Maven Publications. * To avoid [this](https://github.com/gradle/gradle/issues/1118) issue, which can cause transitive dependencies of your published artifacts not to be included, make sure to apply the *java-library* plugin to your build script. Applying the plugin resolves the issue for Gradle version 3.4 and above. For Gradle versions below 3.4, you can use [this](https://gist.github.com/bugs84/b7887fb5d7f9f2d484b8) workaround. * Ivy Publications are not supported. - +* Signing Maven publications with GPG is currently [not supported](https://docs.gradle.org/current/userguide/signing_plugin.html), which is important for syncing to Maven Central. You can setup Bintray to sign automatically any uploaded packages for you by following [these instructions](https://blog.bintray.com/2014/02/11/bintray-as-pain-free-gateway-to-maven-central/). + * Note that you must export a GPG private key that does not include a passphrase to Bintray. + * You must edit the repository to enable uploaded packages to be automaticaly signed. + * The new settings will take into effect for new uploads only. + Below you can find an example for Maven Publication that can be added to your Gradle script: ```groovy