You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/12/12 13:07:44 UTC
[jira] Created: (SLING-769) Upgrade Jackrabbit Dependency to 1.5
Upgrade Jackrabbit Dependency to 1.5
------------------------------------
Key: SLING-769
URL: https://issues.apache.org/jira/browse/SLING-769
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR Webdav 2.0.2, JCR OCM 2.0.2, JCR Jackrabbit Server 2.0.2, JCR Jackrabbit Client 2.0.2, JCR Jackrabbit API 2.0.2, JCR Classloader 2.0.2
Reporter: Felix Meschberger
Assignee: Felix Meschberger
The Jackrabbit project has released 1.5 of Jackrabbit. As a consequence we should also upgrade our infrastructure to Jackrabbit 1.5. As a consequence we do not need that jackrabbit.api module anymore, because Jackrabbits jackrabbit.api library has Bundle manifest headers and can now directly be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-769) Upgrade Jackrabbit Dependency to 1.5
Posted by "Alexander Klimetschek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657363#action_12657363 ]
Alexander Klimetschek commented on SLING-769:
---------------------------------------------
Please make sure the new jsr283 classes/interfaces are exported so that people can use the new ACL/UserManager features from jackrabbit 1.5, even if they are not final yet.
> Upgrade Jackrabbit Dependency to 1.5
> ------------------------------------
>
> Key: SLING-769
> URL: https://issues.apache.org/jira/browse/SLING-769
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Classloader 2.0.2, JCR Jackrabbit API 2.0.2, JCR Jackrabbit Client 2.0.2, JCR Jackrabbit Server 2.0.2, JCR OCM 2.0.2, JCR Webdav 2.0.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> The Jackrabbit project has released 1.5 of Jackrabbit. As a consequence we should also upgrade our infrastructure to Jackrabbit 1.5. As a consequence we do not need that jackrabbit.api module anymore, because Jackrabbits jackrabbit.api library has Bundle manifest headers and can now directly be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-769) Upgrade Jackrabbit Dependency to 1.5
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657367#action_12657367 ]
Felix Meschberger commented on SLING-769:
-----------------------------------------
Thanks for the reminder.
The classes (interfaces mostly) are part of the jackrabbit-api, which is an OSGi bundle as of 1.5. So the Sling jcr/jackrabbit-api bundle will be phased out not be used any more.
> Upgrade Jackrabbit Dependency to 1.5
> ------------------------------------
>
> Key: SLING-769
> URL: https://issues.apache.org/jira/browse/SLING-769
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Classloader 2.0.2, JCR Jackrabbit API 2.0.2, JCR Jackrabbit Client 2.0.2, JCR Jackrabbit Server 2.0.2, JCR OCM 2.0.2, JCR Webdav 2.0.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> The Jackrabbit project has released 1.5 of Jackrabbit. As a consequence we should also upgrade our infrastructure to Jackrabbit 1.5. As a consequence we do not need that jackrabbit.api module anymore, because Jackrabbits jackrabbit.api library has Bundle manifest headers and can now directly be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.