[
https://issues.apache.org/jira/browse/JCR-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781930#action_12781930
]
Sébastien Launay commented on JCR-2389:
---------------------------------------
> I'd very much prefer httpclient 4.0 to be used.
I just created JCR-2406 feel free to provide a patch tested against multiple
WebDAV clients.
> About Derby.
I agree that this dependency is needed only at runtime and only if it is used
in a PersistenceManager/DataStore.
But removing it or rendering it optional implies a non working use of new
TransientRepository() with jackrabbit-core (and also by transitivity
jackrabbit-webapp/standalone).
Maybe the solution is to remove the default repository.xml (only for testing
purpose) and force the user to specify one.
But this leads to a more difficult first approach of Jackrabbit (first hops).
> 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 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.
