Skip to content
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

Feature request: Maven central #184

Open
seanmcl opened this issue Jul 26, 2017 · 2 comments
Open

Feature request: Maven central #184

seanmcl opened this issue Jul 26, 2017 · 2 comments

Comments

@seanmcl
Copy link
Contributor

seanmcl commented Jul 26, 2017

Is there any hope this library will make it to maven central any time soon? All of our other dependencies are available there. I'm getting pushback trying to import this library because it requires a lot of churn in our build system.

Thanks!

@bkrodgers
Copy link
Contributor

We decided to go with Bintray/JCenter instead of pushing to Maven Central awhile ago. I wasn't that directly involved in that decision but unfortunately those who were have all left. I'm not opposed to revisiting it, but I can't commit to if or when that would happen.

Do you have an approval process that prevents you from pulling it from JCenter? In SBT it should just be as simple as adding Resolver.jcenterRepo to your resolvers. But I do know lots of orgs have a requirement to pull everything through a company managed repo.

@seanmcl
Copy link
Contributor Author

seanmcl commented Jul 27, 2017

We're using Bazel, with https://github.com/johnynek/bazel-deps for our maven dependencies. There's some bug with that project that doesn't handle multiple resolvers. I'm working on a fix for that, but in the meantime if it's possible for you to just push a button to publish to maven central, that would be much preferable. I'd be happy to do any work required for this if your team is amenable!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants