Fix remaining Maven dependency convergence issues #153
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.
Summary
This PR resolves three Maven dependency convergence errors reported in version 1.5.3:
jsr305: 3.0.1 vs 3.0.2gson: 2.8.9 vs 2.11.0protobuf-java: 3.25.8 vs 4.32.1Changes
build.gradle:
jsr305andfindbugs annotationsexclusions toprotovalidatedependencyprotobuf-javaandgsonexclusions toprotobuf-java-utildependencyprotobuf-javaexclusion toproto-google-common-protosdependencyjsr305:3.0.2dependencyTesting with Maven Local
To test locally with Maven enforcer plugin:
The three reported conflicts should be resolved. Note that three additional conflicts (
error_prone_annotations,guava,j2objc-annotations) also appear but these existed before this PR and were not reported by users.Related
Addresses remaining issues from #152