[
https://issues.apache.org/jira/browse/SLING-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574572#action_12574572
]
Felix Meschberger commented on SLING-185:
-----------------------------------------
Moved implementation stuff from jcr/api to jcr/base in Rev. 633140 and 633141.
Adapted jcr/jackrabbit-client module in Rev. 633143. and jcr/jackrabbit-server
module in Rev. 633145.
> Split jcr/api project in two
> ----------------------------
>
> Key: SLING-185
> URL: https://issues.apache.org/jira/browse/SLING-185
> Project: Sling
> Issue Type: Improvement
> Components: Repository
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> SLING-176 asks for the removal of the jackrabbit-jcr-commons classes from the
> exports of the jcr/api bundle on the basis of a discussion to clearly
> separate API and implementation stuff.
> Along those lines, we should probably go a step further and split the jcr/api
> bundle in two:
> * jcr/api - just exports JCR and Jackrabbit API
> * jcr/base - provides node type definition and session pooling
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
