[
https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798089#action_12798089
]
Jukka Zitting commented on JCR-2362:
------------------------------------
It's probably impossible to define a generic "single jar" solution for remote
clients. Even if you accept the overhead of unnecessary dependencies for remote
access protocols you don't need, you still need to worry about things like
logging tools and potential duplicate dependencies.
I would rather leave it to build tools like Maven to keep track of required
dependencies for anything other than ad-hoc example code. For such use cases
you can always use the standalone jar as a solution that covers everything you
need in the classpath.
> Drop the jackrabbit-jcr-client component
> ----------------------------------------
>
> Key: JCR-2362
> URL: https://issues.apache.org/jira/browse/JCR-2362
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-client
> Reporter: Jukka Zitting
>
> The new GenericRepositoryFactory class and JcrUtils.getRepository methods
> introduced in JCR-2360 implement an improved version of the
> jackrabbit-jcr-client functionality.
> Thus I propose that we drop the jackrabbit-jcr-client component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
