-
Notifications
You must be signed in to change notification settings - Fork 75
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
okhttp-digest unresolvable on maven central #817
Comments
That artifact is not currently published to Maven Central, but is published to JCenter. Add this repository to your pom.xml repostories section:
|
@tdiepenbrock, are there better ways we can advertise such requirements? We included it on http://developer.marklogic.com/products/java , but maybe we should have it somewhere else also... Where did the customer go to download 4.0.2? |
It's worth creating a ticket asking them to publish to Maven Central.Bintray makes it really easy. Then it would resolve and "just work" without custom repository config. |
Hi Sam,
It looks like the customer relies on Maven Central for everything. They did not pull from the separate repo. I’ll find out more tomorrow when we have our regularly scheduled conference call with them.
td
Thomas Diepenbrock
Technical Manager
MarkLogic Corporation
Thomas.Diepenbrock@marklogic.com<mailto:Thomas.Diepenbrock@marklogic.com>
Cell: +1 703 980 1248
[cid:0B48B25A-8630-42FD-BFB9-3092CB213523] <http://www.marklogic.com/social/>
<http://www.marklogic.com/social/>
On Sep 18, 2017, at 12:32 PM, Sam Mefford <notifications@github.com<mailto:notifications@github.com>> wrote:
@tdiepenbrock<https://github.com/tdiepenbrock>, are there better ways we can advertise such requirements? We included it on http://developer.marklogic.com/products/java , but maybe we should have it somewhere else also... Where did the customer go to download 4.0.2?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#817 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AH7cXQ7d0vWXkFIAfrfK2TFU0MmB9xkaks5sjpsegaJpZM4Pa_kG>.
|
Is this still an issue? It’s not really in our control, as it’s a descendent ancestor. |
Our customer is at a dead stop because com.burgstaller:okhttp-digest:jar:1.14 can't be resolved on maven central.
The text was updated successfully, but these errors were encountered: