-
Notifications
You must be signed in to change notification settings - Fork 72
okhttp-digest coordinates have changed #1298
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
Comments
Note that this is an issue for me right now as I try to upgrade ml-javaclient-util to Java Client 5.4.0 and not use "jcenter()" as a repository. If I try to run a test using ml-javaclient-util, I get an error since okhttp-digest cannot be resolved, as its coordinates have changed. So in order for ml-javaclient-util to stop using jcenter(), I have to modify its build.gradle script to bring in the updated version of okhttp-digest. |
Here's what I'm doing to workaround the problem:
|
Related to: #1230 Assuming (if and only if) the latest of all dependencies of the Java API are available on Maven Central, the build.gradle files for the Java API should just remove JCenter as a repository. |
…klogic#1272 Previous change had line ending issue on windows
…klogic#1272 Previous change has line ending issue on windows
…klogic#1272 Previous change has line ending issue on Windows
Previous change had line ending issue on windows
Previous change has line ending issue on windows
Previous change has line ending issue on Windows
Was able to run tests (Dev. team's JUnit tests) successfully and make zip file distribution. The zip file contains okhttp-digest version 2.5 jar file. |
There's no server-side change in this issue. |
This is really just a note - see https://github.com/rburgst/okhttp-digest - the coordinates of okhttp-digest have changed with its move from jcenter to mavenCentral.
The scope of this ticket could also be larger - i.e. remove "jcenter()" from java-client-api and update any needed dependencies (such as okhttp-digest) and verify that the code still compiles, tests still work, and artifacts can still be assembled.
The text was updated successfully, but these errors were encountered: