jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christophe Lombart (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1115) Remove dependency on Jackrabbit-core
Date Sun, 14 Oct 2007 07:44:50 GMT

     [ https://issues.apache.org/jira/browse/JCR-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christophe Lombart resolved JCR-1115.
-------------------------------------

    Resolution: Fixed

>From now, Jackrabbit dependencies are used only in the unit tests. 

I propose to refactor the jcr-nodemanagement subproject only if others implementation are
supported. 

> Remove dependency on Jackrabbit-core
> ------------------------------------
>
>                 Key: JCR-1115
>                 URL: https://issues.apache.org/jira/browse/JCR-1115
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jcr-mapping
>            Reporter: Christophe Lombart
>             Fix For: 1.4
>
>
> We should remove the dependency on Jackrabit core in the OCM subprojects "jcr-mapping"
and "annotation". We can use Jackrabbit core only for the unit tests. 
> We can also split the jcr-nodemanagement into several subprojects (one per JCR repo impl).
 We will have only one subproject for Jackrabbit but contributions for other JCR repo impl
are welcome.  A specific jcr-nodemanagement jar can be produce for each JCR repo impl. When
the JCR will support the node creation, we can refactor the jcr-nodemanagement. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message