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.
Consider adding JCenter to the list of default resolvers
See original GitHub issueI remember that at some point JCenter was in the list of default resolvers, but I missed that it was removed and only recently discovered this:
I understand that there were some problems with making JCenter the new default resolver and replacing Maven Central, but I don’t quite understand why it cannot be just another resolver in the default chain. Could it be added again (in addition to Maven Central) or it is unlikely for some technical reason?
Note, useJCenter setting is not a solution. I’d like to be able to publish to JCenter without forcing users to use useJCenter := true or resolvers += Resolver.jcenterRepo.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:15 (9 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
@brianf On behalf of Scala community, I just wanted to say thanks to you and Sonatype for all the work and funding on Maven Central.
As per this issue, I think we can safely close this as wontfix.
As a follow up, anyone here interested in the history of Central, I was recently on a podcast describing it. https://manifest.fm/6