jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2389) Update dependency versions for commons-collections, slf4j and derby
Date Tue, 24 Nov 2009 13:22:39 GMT

    [ https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781909#action_12781909

Thomas Mueller commented on JCR-2389:

No objections for the patch.

About Derby: Derby is not required to compile Jackrabbit. It is required when running the
tests (that's why I wrote <scope>test</scope>). And it is used as the default
persistence manager, so jackrabbit-standalone (?) should include Derby. However, Derby is
not required at runtime if you configure a different persistence manager. In the long term,
I believe the Derby dependency within jackrabbit-core should be <scope>test</scope>
and not anything else. Short term, it doesn't really matter.

> 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, JCR-2389-update-dependencies-2009-11-18_2.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 to
> 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.

View raw message