jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-87) Move to a newer vesion of Commons Collections
Date Sat, 02 Apr 2005 13:50:36 GMT
     [ http://issues.apache.org/jira/browse/JCR-87?page=comments#action_62030 ]
     
Jukka Zitting commented on JCR-87:
----------------------------------

Is there some added benefit in upgrading? AFAIK you should be able to just replace the commons-collections
2.1 jar with a newer jar in the classpath if you want to use newer features (commons-collections
should mostly be backwards compatible).

As long as Jackrabbit only specifies the build dependencies and not the runtime dependencies,
I see this issue as a "don't break it if it works" case. :-)

But if you think that upgrading the dependency and possibly using the refactored classes would
be beneficial also to the Jackrabbit internals, then I see no problem in accepting the change.


> Move to a newer vesion of Commons Collections
> ---------------------------------------------
>
>          Key: JCR-87
>          URL: http://issues.apache.org/jira/browse/JCR-87
>      Project: Jackrabbit
>         Type: Wish
>     Reporter: Edgar Poce
>     Priority: Minor
>  Attachments: 05-04-02-upgradeCommonsCollections.patch
>
> It would be useful if the developer wants to use jackrabbit in an application that uses
a newer version of this library.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message