-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Bintray publish settings #501
Conversation
@@ -1,35 +1,31 @@ | |||
language: scala |
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.
supernit: can you get rid of the fuzz here? looks like the only needed one is the last few lines.
Thanks for giving this a go, @jamescway! I think once you rebase against upstream master, this gets smaller. I've made some notes, mostly on cleanup. |
having some problems after rebase... With the newer lib here's the full stack trace
Seems like maybe the lib bintry is using an old version of dispatch maybe? |
looks like we have netty-3.10.1.Final.jar and async-http-client-1.8.10.jar both loading netty |
Where does async-http-client come from? Should be easy to replace with finagle-http if we have control over the source. |
Aah, I think I can spot the problem - publish to bintray uses Dispatch, while Scrooge uses Finagle (with an older version of Netty, probably) |
Could an exclude on scrooge work? I doubt the compiler actually needs to
load the netty classes. I can give this a try in 30m or so, if no one else
does.
|
@eirslett yeah, dispatch uses it, I have a PR merged into bintry going to find out if he will release it. Actually scrooge has the newer version of netty, bintry (dep of bintray-sbt has an older version. @adriancole rolling back and using scrooge-sbt-plugin" % "3.16.3" would solve the problem in the meantime What do u guys think? Going to roll it back to 3.16.3 feel free to thumbs down :p |
|
This probably isn't going to work now that #503 has been merged <_< |
OTOH Bintray publishes an official Gradle plugin: https://bintray.com/jfrog/jfrog-jars/gradle-bintray-plugin |
After update to use gradle #503, much of this stuff is not relevant, going to close and start another PR |
@abesto just noticed that tool, I'll give it a shot |
Problem
We need to release artifacts built in travis to Bintray openzipkin/zipkin repo.
Solution
How it works
git tag v1.2.3
git push origin master --tags
gem install travis
travis encrypt BINTRAY_API_KEY=<Bintray API key>--add
travis encrypt BINTRAY_USER="<Bintray username" --add
Caveats