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/03/03 16:56:51 UTC
[jira] Closed: (SLING-185) Split jcr/api project in two
[ https://issues.apache.org/jira/browse/SLING-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-185.
-----------------------------------
Resolution: Fixed
Separation of api and implementation now done. So this may be closed.
> 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.