Handle transitive buildscript dependencies that were only present in JCenter #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change fixes the broken Samza build by rewriting some buildscript dependencies that were only present in JCenter, which is now shutdown. In particular,
com.burgstaller:okhttp-digest:1.10
andorg.ysb33r.gradle:grolifant:0.12
, transitive dependencies ofcom.github.jruby-gradle:jruby-gradle-plugin:2.0.2
, only existed in JCenter.The change:
okhttp-digest
fromcom.burgstaller
toio.github.rburgst
okhttp-digest
from1.10
to1.21
grolifant
from0.12
to0.12.1
Ideally,
jruby-gradle-plugin
, which transitively depends on these plugins would be updated to resolve these issue, but this change fixes the problems in the meantime. The plugin has not been updated or released in quite some time. This PR has not well-tested to see how compatible these new versions are with the Samza build.For more information, see: