-
Notifications
You must be signed in to change notification settings - Fork 1
Update OKHTTP dependency #5
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
Conversation
While at it remove requirement for scijava-common version as it is managed
Signed-off-by: tferr <tiago.tferr@gmail.com>
This requires scijava/scijava-io-http#5 to be accepted and merged!
Good idea! |
@tferr Argh, I didn't notice that you bumped the version number. You shouldn't do this manually. Use the |
@ctrueden , I did use the release-version.sh script: Forked the project. did the changes, ran release-version.sh, started the PR. How did I manage to screw up? |
The Anyway, no worries—I cut the release myself, resetting the master branch's SNAPSHOT back to 0.2.2-SNAPSHOT again, so no harm done. 👍 |
@tferr I did notice one worrisome thing, though: a
However, it seems that version 0.2.0 also emits this exception. And it does not fail any tests. I don't suppose you looked at the code carefully enough to verify whether that's supposed to happen? @gab1one Do you remember? I generally try to avoid dumping exceptions to the console when they are expected, in favor of catching them... |
@ctrueden, no I did not peruse the code. I looked for deprecations and tests completion. I also saw that exception but because it was also happening with the old okhttp version, I didn't think much of it. |
@gab1one, @ctrueden :
SNT uses okhttp a lot. We are currently using v4.7.2. There is a funky issue in some combinations of update sites (I really didn't have time to look into it: it was hard to understand how it was happening) the okhttp jar from our update site does not get downloaded: the updater considers the okhttp from scijava-io-http instead. This attempts to bring them into sync. Eitherway, you guys are using a 3year old release, so updating is certainly beneficial!