You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2010/12/16 11:40:02 UTC
[jira] Created: (ISIS-51) Standardize on just one collections API
(either google-collections/guava or Apache collections)
Standardize on just one collections API (either google-collections/guava or Apache collections)
-----------------------------------------------------------------------------------------------
Key: ISIS-51
URL: https://issues.apache.org/jira/browse/ISIS-51
Project: Isis
Issue Type: Improvement
Reporter: Dan Haywood
Priority: Minor
Currently we use both.
For what it's worth, my vote is for google-collections (which is now a subset of guava) rather than the Apache commons collections. Two reasons:
1. I think it's been better quality
2. the guava library is likely to give us some further general language utilities, meaning we can may be able to delete some stuff in org.apache.isis.core.commons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ISIS-51) Standardize on just one collections API
(either google-collections/guava or Apache collections)
Posted by "Dan Haywood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ISIS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-51:
----------------------------
Component/s: isis-parent (build plugins + site)
Have moved to isis-parent, since will impact several modules. Probably no need for this to be an umbrella; I don't think we use Apache commons collections in too many places.
> Standardize on just one collections API (either google-collections/guava or Apache collections)
> -----------------------------------------------------------------------------------------------
>
> Key: ISIS-51
> URL: https://issues.apache.org/jira/browse/ISIS-51
> Project: Isis
> Issue Type: Improvement
> Components: isis-parent (build plugins + site)
> Reporter: Dan Haywood
> Priority: Minor
>
> Currently we use both.
> For what it's worth, my vote is for google-collections (which is now a subset of guava) rather than the Apache commons collections. Two reasons:
> 1. I think it's been better quality
> 2. the guava library is likely to give us some further general language utilities, meaning we can may be able to delete some stuff in org.apache.isis.core.commons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.