-
Notifications
You must be signed in to change notification settings - Fork 640
Use common bintray package #29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -27,7 +27,8 @@ script: | |||
deploy: | |||
provider: script | |||
script: | |||
- sbt -J-XX:ReservedCodeCacheSize=128m +publish bintraySyncMavenCentral | |||
# do the maven central sync only once, as all of the artifacts are under the same bintray package | |||
- sbt -J-XX:ReservedCodeCacheSize=128m +publish amqp/bintraySyncMavenCentral |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so this is only to publish amqp?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of the subprojects share the same bintray package. So calling this task on one subproject will sync all of the artifacts in the bintray package.
Calling the aggregate bintraySyncMavenCentral
task (for all subprojects) results in:
[error] (cassandra/*:bintraySyncMavenCentral) failed to sync akka/alpakka@0.1-RC2 with maven central: {"status":"Sync Failed","messages":"[Failed to close repository: comlightbend-1028. Server response:\n <nexus-error>\n <errors>\n <error>\n <id>*<\u002fid>\n <msg>Unhandled: Staging repository is already transitioning: comlightbend-1028<\u002fmsg>\n <\u002ferror>\n <\u002ferrors>\n<\u002fnexus-error>, Dropping existing partial staging repository.]"}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just like it said in the comment, sorry I didn't read
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, reading comments is over rated ;-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -27,7 +27,8 @@ script: | |||
deploy: | |||
provider: script | |||
script: | |||
- sbt -J-XX:ReservedCodeCacheSize=128m +publish bintraySyncMavenCentral | |||
# do the maven central sync only once, as all of the artifacts are under the same bintray package | |||
- sbt -J-XX:ReservedCodeCacheSize=128m +publish amqp/bintraySyncMavenCentral |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why amqp here?
@@ -27,7 +27,8 @@ script: | |||
deploy: | |||
provider: script | |||
script: | |||
- sbt -J-XX:ReservedCodeCacheSize=128m +publish bintraySyncMavenCentral | |||
# do the maven central sync only once, as all of the artifacts are under the same bintray package | |||
- sbt -J-XX:ReservedCodeCacheSize=128m +publish amqp/bintraySyncMavenCentral |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, reading comments is over rated ;-)
So all of the subprojects can be released at once, and new subprojects do not need maintenance when being released the first time (like requesting new bintray package to be included into JCenter).