You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2014/07/14 17:32:05 UTC
[jira] [Commented] (WICKET-5641) Add Google Guava dependency.
[ https://issues.apache.org/jira/browse/WICKET-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060758#comment-14060758 ]
Martin Grigorov commented on WICKET-5641:
-----------------------------------------
I'm -1 to add Guava as dependency to Wicket core.
My reason is explained earlier at http://markmail.org/message/qmoebzwoi3cejcc2.
I have seen many OSS projects using old version of Guava just because the feature(s) they use have been removed/reworked in the next version of Guava without replacement.
JarJar-ing Guava into Wicket is an option but this will make wicket-util.jar way too big.
> Add Google Guava dependency.
> ----------------------------
>
> Key: WICKET-5641
> URL: https://issues.apache.org/jira/browse/WICKET-5641
> Project: Wicket
> Issue Type: Wish
> Components: wicket
> Affects Versions: 7.0.0-M2
> Reporter: Garret Wilson
> Priority: Minor
> Labels: core, dependencies, guava, library
>
> The Google [Guava library|https://code.google.com/p/guava-libraries/] has grown popular over the last few years. Besides providing common day-to-day boilerplate such as {{Preconditions}} and comparator helpers such as {{Ordering}}, it also provides a diverse set (pun unintended) of tested useful collections such as {{Multimaps}}.
> Pulling in a new significantly-sized dependency would be advised only if it is useful. This JIRA is to serve as a list of places in Wicket where the Guava library would prove beneficial, as well as to provide a forum for developer comment on the desirability of adding such a dependency.
--
This message was sent by Atlassian JIRA
(v6.2#6252)