Set up Maven distribution for new plugins

Summary:
Setting up the necessary metadata to publish the separate plugins
to Maven/Bintray.

Reviewed By: danielbuechele

Differential Revision: D17480263

fbshipit-source-id: 1772cee5b3744ce52fc6e2510a27cb7f500e72bf
This commit is contained in:
Pascal Hartig
2019-09-20 06:05:13 -07:00
committed by Facebook Github Bot
parent 2baadf9867
commit 1ab47f9ca8
7 changed files with 46 additions and 1 deletions

View File

@@ -16,5 +16,8 @@ elif [ "$IS_SNAPSHOT" != "" ]; then
exit 1
else
openssl aes-256-cbc -d -in scripts/bintray-publish-keys.enc -k "$ANDROID_PUBLISH_KEY" >> "$BASEDIR/gradle.properties"
"$BASEDIR"/gradlew :android:bintrayUpload :noop:bintrayUpload -PdryRun=false
# Need to list the projects individually here because of a bug in the gradle-bintray-plugin that
# tries to upload projects not meant for distribution (like our root project) and throws an NPE
# in that case.
"$BASEDIR"/gradlew :android:bintrayUpload :noop:bintrayUpload :fresco-plugin:bintrayUpload :network-plugin:bintrayUpload :litho-plugin:bintrayUpload -PdryRun=false
fi