You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can we freeze the release version of guava-retrying on a release version of guava? Current setup leads to potential instabilities in case there is a breaking change in the edge version of the underlying dependency.
The workaround in my project pom.xml was to exclude the guava dependency as defined
We've had a similar issue. On a larger scale, is guava-retrying using Guava that much to really require Guava? That is, would it make sense to create a utils class with the Guava stuff being used? Guava is a very common library used by projects that uses guava-retrying. One less potential Guava version conflict would be nice.
Let me know if this would make sense I might be able to have a quick glance over the code to see if this refactoring is a lot of work or not.
With the current configuration of the gradle build file, the dependency on the google guava library currently resolves to 20.0-SNAPSHOT
Can we freeze the release version of guava-retrying on a release version of guava? Current setup leads to potential instabilities in case there is a breaking change in the edge version of the underlying dependency.
The workaround in my project pom.xml was to exclude the guava dependency as defined
The text was updated successfully, but these errors were encountered: