What existing classes could be substituted by guava classes? I don't think it would be sensible to replace 3 or 4 classes with a 2-million-byte library :)
“The truth is rarely pure and never simple.” ― Oscar Wilde On Sun, Jul 13, 2014 at 2:13 PM, Garret Wilson <gar...@globalmentor.com> wrote: > On 7/13/2014 8:49 AM, Sven Meier wrote: >> >> ... >> >> for null checking we have our own solution, see >> org.apache.wicket.util.lang.Args#notNull(). > > > Great! I'll start using Args with code I submit. > > Has there been any discussion on including Google Guava as a dependency? > > Years ago I rolled all my own collection utilities and such, but I finally > came around to using Guava. All that stuff is just so hard to maintain, but > it's also hard to live without. > > * The Multimap classes (in which each key can have a collection of > values) as just one example is so convenient. > * And its MapMaker allows for easy creation of concurrent maps with > e.g. weak keys. (The weak hash maps Java offers don't use identity > for keys, which can create some really unexpected behavior and bugs.) > * Oh, and its ImmutableSet factory methods are so handy... > > > Anyway, Guava is hard to live without at this point, and I'm even > considering (gasp!) including it as a dependency in my own personal code and > abandoning a lot of the utilities I've created over the years. :) Any > thoughts on this for Wicket 7.x? > > Garret
