Google: Drop old jwt-core dependencies #2641
Merged
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 drops the
jwt-core
dependency from the Google connectors since this is now handled ingoogle-common
.Unfortunately, this is currently a potentially fatal bug: the
google-common
module depends on a recent version ofjwt-scala
that has a new Maven organization name but retains the same package name asjwt-core
, which IIUC creates a classpath conflict that SBT will not automatically resolve via eviction. Due to API changes, if the oldJWT
classes are used instead of the new then authorization requests to Google will fail.