I love Guava but from a systems perspective I dread it because many products are stuck on old versions of Guava, particularly Hadoop
https://issues.apache.org/jira/browse/HADOOP-10101 it is stuck on 11.0.2 and it's not just hypothetical that it has to be there because if you use the next version up the tests fail for HDFS. My own toolset is set up in a somewhat awkward way so that I can use 11.0.2 for things that run in cluster and have everything that runs out-of-cluster using 18.0. The Google folks do give warning about breaking changes ahead of time but they do make breaking changes, and the general popularity of Guava tends towards the creation of "dependency hell" On Tue, Dec 23, 2014 at 12:36 PM, Kristian Rosenvold <[email protected]> wrote: > Since jena is reasonably progressive wrt jdk I'd probably give that > move an extra thought: jdk8 makes most of guava "obsolete", outdated > or cumbersome. In our jdk8-based code base we generally found apache > commons-lang/io + java8 to be a much more pleasing combination. > > Kristian > > > 2014-12-23 17:32 GMT+01:00 Andy Seaborne <[email protected]>: > > I've added Guava as a managed dependency in jena-parent. The license is > > Apache 2.0. > > > > Andy > -- Paul Houle Expert on Freebase, DBpedia, Hadoop and RDF (607) 539 6254 paul.houle on Skype [email protected] http://legalentityidentifier.info/lei/lookup
