Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Please consider publishing to Maven Central
See original GitHub issueIt isn’t a problem for a library to add resolvers += "johnreed2 bintray" at "http://dl.bintray.com/content/johnreed2/maven" (by the way, isn’t the equivalent needed for Maven as well)? It is a bit worse to require everyone who depends on this library to add it too. I was thinking how I could avoid this problem, but can’t find a reliable way 😦 Though SBT does allow to make this dependency for SNAPSHOT versions only.
See https://bintray.com/docs/usermanual/uploads/uploads_syncingartifactswithmavencentral.html and https://blog.bintray.com/2014/02/11/bintray-as-pain-free-gateway-to-maven-central/ for explanation how to upload from Bintray to Maven Central.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Success! https://drive.google.com/file/d/0B1IimJ20gG0SVWdnRDM1R1N0Y2s/view?usp=sharing
@alexeyr @timcharper Hey guys, I am really close. I uploaded to bintray and got the gpg keys set up in the 4.0 branch. Calling “publish-signed” with the sbt-pgp plugin generates this pom file, but when I try to sync from bintray to maven central, I get this error message.