You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/10/23 17:05:00 UTC
[jira] Created: (JCR-2362) Drop the jackrabbit-jcr-client component
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.
[jira] Resolved: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved JCR-2362.
-------------------------
Resolution: Later
the component was released in jackrabbit 2.0 -> resolving issue.
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798557#action_12798557 ]
Tobias Bocanegra commented on JCR-2362:
---------------------------------------
i disagree - a simple solution could be to use osgi to hide all dependencies,
another to have a simple private classloader for them.
of course thise single-jar might not be small - (like most of the jdbc drivers).
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770662#action_12770662 ]
Tobias Bocanegra commented on JCR-2362:
---------------------------------------
-1 for removing it
afaik, the goal of this component was, that it should be a single jar, that includes all code that is needed to access a jr repository remotely.
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770915#action_12770915 ]
Jukka Zitting commented on JCR-2362:
------------------------------------
I think I see Toby's point. We can turn jackrabbit-jcr-client into a composite jar like jackrabbit-standalone. Then it certainly makes sense to keep it and provide it as one of the main binary downloads on the Jackrabbit download page.
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769985#action_12769985 ]
Marcel Reutegger commented on JCR-2362:
---------------------------------------
+1
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770830#action_12770830 ]
Thomas Mueller commented on JCR-2362:
-------------------------------------
> access a jr repository remotely
And you can't do that with JcrUtils.getRepository?
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770891#action_12770891 ]
Tobias Bocanegra commented on JCR-2362:
---------------------------------------
i try to explain it better.
the idea is to have 1 jar (like a jdbc driver) that encapsulates all code (but nothing more) that allows you to access a repository remotely.
all you will need in your classpath is the jackrabbit-jcr-client.jar and the jcr.jar.
preferably, it will also contain some classloader magic, that hides the client classes from the overall classpath. so that it can be used in
projects where other libs are present (e.g. hide commons-io).
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769956#action_12769956 ]
Thomas Mueller commented on JCR-2362:
-------------------------------------
+1
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799150#action_12799150 ]
Jukka Zitting commented on JCR-2362:
------------------------------------
I'm not opposed to adding a new OSGi or standalone bundle that combines multiple client libraries, but that's not what jackrabbit-jcr-client currently is. I wouldn't like to release the component in Jackrabbit 2.0 since it obviously still doesn't meet the goal of being "a single jar, that includes all code that is needed to access a jr repository remotely". If we release it now as-is, then making substantial changes (like inlining dependencies) to it later in the 2.x release cycle becomes quite troublesome.
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782881#action_12782881 ]
Michael Dürig commented on JCR-2362:
------------------------------------
+1 for removing it in the current form. ATM it is far from what Tobias is suggesting. So I think we better remove it and create (tracked by a separate issue) a new module which covers Tobias' needs.
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770911#action_12770911 ]
Marcel Reutegger commented on JCR-2362:
---------------------------------------
The same is now true for jackrabbit-jcr-commons and JcrUtils.getRepository(). The only dependency of jcr-commons is the JCR API.
> 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.
[jira] Commented: (JCR-2362) Drop the jackrabbit-jcr-client
component
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799147#action_12799147 ]
Felix Meschberger commented on JCR-2362:
----------------------------------------
Providing a simple single client JAR might be helpful to the uninitiated. But this should only contain a single method of accessing a remote repository. Nothing fancy, but something to get started quickly.
Of course, this jar file can be an OSGi bundle probably not exporting anything- yet registering a service to access the repository.
For more customized setups and multiple access protocols, we should really leave it to the downstream developers.
But, I would discourage any classloader hacking stuff or some multi-mechanism, big, fat JAR approach.
> 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.