As I just said, using it as a library and not leaking stuff should be ok. But some of the guava stuff has a tendency to leak the moment you start using it. And it should probably be shaded to avoid version conflicts. And shading this stuff has traditionally led to a full copy of everything, since they use "facade" classes with static builders that basically depend on everything, so getting "just" those classes you need is a lot harder than it could have been otherwise.
I was only referring to 1.7 in the positive sense;- it's one step closer to the next "good thing" in java 1.8. Jena will be there in a year or two. Given our pace in maven we'll get there around when I start looking for a retirement home in the mountains somewhere :) Kristian 2014-12-24 23:40 GMT+01:00 Benson Margulies <bimargul...@gmail.com>: > On Wed, Dec 24, 2014 at 5:38 PM, Kristian Rosenvold > <krosenv...@apache.org> wrote: >> I do most my work in a project that is just now discussing moving from >> 1.5 to 1.6, so I find "1.7" to be an exotic choice :) >> >> I suppose shading in a few classes for caching is ok. I think using >> any of the functional stuff or the collections is a bad choice >> currently. > > Contrarywise, I work with a ton of code that uses Guava as the assumed > framework. I don't see anyone trying to use Jena inside the > implementation of Maven :-). I don't see a problem with Jena just > depending on it. > > > >> >> Kristian >> >> >> 2014-12-24 19:06 GMT+01:00 Andy Seaborne <a...@apache.org>: >>> On 24/12/14 05:47, Stian Soiland-Reyes wrote: >>>> >>>> Will JDK8 become a requirement before Jena 2? I would hope not >>>> immediately, >>>> JDK7 is still a very large install base (if not the largest). >>> >>> >>> No one has suggested it. It is not that long ago we moved to requiring Java >>> 7. >>> >>> Generally, it's been "last 2 supported versions" though it's easier to have >>> that rule then apply it as it needs to factor in take up across all JVMs. >>> >>> (The Web says) Java 9 is scheduled for Autum 2016. >>> >>> Andy >>> >>> I just found out: >>> """ >>> Complete the removal, begun in Java SE 8, of underscore from the set of >>> legal identifier names. >>> """ >>> Andy >>> >>> >>>> On 23 Dec 2014 11:36, "Kristian Rosenvold" <krosenv...@apache.org> 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 <a...@apache.org>: >>>>>> >>>>>> I've added Guava as a managed dependency in jena-parent. The license is >>>>>> Apache 2.0. >>>>>> >>>>>> Andy >>>>> >>>>> >>>> >>>
