Make guava dependency configurable (or non strict?)
See original GitHub issueI am using the jib plugin which has a dependency declared to guava
'com.google.cloud.tools.jib:com.google.cloud.tools.jib.gradle.plugin:3.1.4' (runtime) --> 'gradle.plugin.com.google.cloud.tools:jib-gradle-plugin:3.1.4' (runtime) --> 'com.google.guava:guava:30.1.1-jre'
This clashes with the strict configuration of refreshVersions. Is there any way to make this configurable? Or override it somehow?
Issue Analytics
- State:
- Created 2 years ago
- Comments:19
Top Results From Across the Web
How can I force Gradle to set the same version for two ...
One of your dependencies is forcing the guava version to update. Use gradle dependencies to locate which library is evicting your version.
Read more >Customizing resolution of a dependency directly
This section covers mechanisms Gradle offers to directly influence the behavior of the dependency resolution engine. In contrast to the other concepts ...
Read more >Overriding Dependency Versions and Using Version Ranges ...
Get step-by-step guidance on managing dependencies in Maven: declare dependencies, overriding dependency versions, and using version ranges.
Read more >Customizing Dependency Resolution Behavior - API Manual
A configuration can be configured with default dependencies to be used if no dependencies are explicitly set for the configuration. A primary use...
Read more >Java platform plugin constraints Leak · Issue #13078 - GitHub
Could not resolve com.google.guava:guava:{strictly 19.0}. Required by: ... Dependency path 'gradle-constraints-leak:projectB:unspecified' ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Resolution just released in 0.40.1!
Thanks for pushing this issue through!
I’m happy that it’s now the past and that refreshVersions also got smaller by dropping that avoidable dependency.