You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Sébastien Launay (JIRA)" <ji...@apache.org> on 2009/11/18 10:00:40 UTC
[jira] Updated: (JCR-2389) Update dependency versions for
commons-collections, slf4j and derby
[ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sébastien Launay updated JCR-2389:
----------------------------------
Attachment: JCR-2389-update-dependencies-2009-11-18.patch
I agree that using old release of libraries can be painful in an application when you do not have access to separate classloader mechanism (like in OSGI) and you use additional libraries with conflicting dependencies.
I think that upgrading runtime transitive dependencies can be done in the 2.0 development branch as this is a major version upgrade from 1.x.
So I proposed the following patch for:
- migrating slf4j dependency from 1.5.3 to 1.5.8
- migrating commons-collections dependency from 3.1 to 3.2.1 with deprecation modifications [1]
this implies a new dependency on commons-beanutils for jackrabbit-core (test) and jackrabbit-webapp
- migrating commons-beanutils (previously not used but defined in jackrabbit-parent) from 1.7.0 to 1.8.2
- migrating jetty dependencies from 6.1.14 to 6.1.22
- migrating xerces dependencies from 2.8.1 to 2.9.0
- removing unused parent dependencies (commons-digester, commons-lang)
- remove duplicates servlet-api and jsp-api dependencies
With this patch applied to trunk build with tests is successful (I just disable the AdministratorTest#testAdminNodeCollidingWithRandomNode test case).
I believe we can also upgrade from commons-httpclient 3.0 to HttpClient 4.0 on jackrabbit-spi2dav with a few modifications.
For Derby, i agree that upgrading is not safe and must be reviewed by a PersistenceManager expert ;).
[1] http://commons.apache.org/collections/api-release/org/apache/commons/collections/BeanMap.html
> Update dependency versions for commons-collections, slf4j and derby
> -------------------------------------------------------------------
>
> Key: JCR-2389
> URL: https://issues.apache.org/jira/browse/JCR-2389
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Affects Versions: 2.0-beta1
> Reporter: Attila Király
> Priority: Minor
> Attachments: JCR-2389-update-dependencies-2009-11-18.patch
>
>
> Some of the dependencies used by the 2.0-beta1 could be upgraded:
> commons-collections from 3.1 to 3.2.1
> slf4j from 1.5.3 to 1.5.8
> derby from 10.2.1.6 to 10.5.3.0
> Not sure about derby but the other two seems to be just drop in replacements for their older verisons.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.