Github user jloisel commented on the issue:
https://github.com/apache/jmeter/pull/221
Guava is highly stable and mature now, incompatible changes are unlikely to
happen. +2MiB of dependencies being added? It's nothing today. Groovy alone
takes 7.0MiB in JMeter. Guava is also already used by JMeter Plugins like
Webdriver, which also uses Guava 19.0. It's up to JMeter plugins developers to
keep up-to-date their plugins, and up to JMeter developers to keep internal
libraries up-to-date.
Calcite is a database framework whose purpose is to be integrated into java
applications. This is not the general case for JMeter. Problems with
dependencies depend on the usage of the library itself.
Caffeine is probably a great caching library which deserves to be used, but
it's its only usage. Guava is a multi-purpose library. It has so many
interesting libraries like high performance immutable collections, String
Joiners and Splitters, Comparable/Comparator made simple through Ordering,
Multimaps, Ranges, great hashing algorithms like MurMur, Preconditions and
more.
Generally speaking, caches should be avoided at all cost as Martin Fowler
said:
> There are only two hard things in Computer Science: cache invalidation
and naming things.
[http://martinfowler.com/bliki/TwoHardThings.html](http://martinfowler.com/bliki/TwoHardThings.html)
:+1: for a migration to Java 8 too, as it would allow to use built-in
Streams, Function, Predicate and more.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---