Reduce Google Guava usage
See original GitHub issueGuava is a commonly used library that can cause dependency conflicts. Reduce the usage of Google Guava in lettuce 4.2 so lettuce can hopefully get rid of it one day:
Lists
andMaps
and immutable collections/maps- Cache and Cache Builder
AbstractInvocationHandler
Preconditions
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Why is there no reduce in Guava library? - Stack Overflow
I want to use functional programming in my Android app and as Java8 is not available I decided to use Guava Library. But...
Read more >Guava Cache - Baeldung
In this tutorial, we'll focus on the Guava Cache implementation, including basic usage, eviction policies, refreshing the cache, and some ...
Read more >Guava Tutorial - Tutorialspoint
Guava is an open source, Java-based library developed by Google. It facilitates best coding practices and helps reduce coding errors.
Read more >Decluttering Google Guava : r/java - Reddit
The main issue is - removing stuff is cool, but it does not solve any particular problem. If anything, it will create work...
Read more >Guava Library in Java - GeeksforGeeks
By replacing the existing library classes with those from guava, you can reduce the amount of code you need to maintain. It is...
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
I’m not avoiding immutable collections/maps but I version conflicts because of Guava. Guava is used nearly everywhere and here and there in a driver or common framework (Cassandra Driver, Vaadin, Jackson, and 11526 other public artifacts according to VersionEye). Some API’s are changing/removed within Guava so upgrading to a higher version carries always the risk of breaking things. I’m also not fan of relocating (shading) 2MB of Guava for “just” a bunch of helpers.
Implemented. The remaining parts use
LoadingCache
andHostAndPort
on the public API.