[
https://issues.apache.org/jira/browse/JCR-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895234#action_12895234
]
Michael Dürig commented on JCR-2692:
------------------------------------
The idea using a released version of jackrabbit-core for testing does not work:
<dependency>
<groupId>org.apache.jackrabbit</groupId>
<artifactId>jackrabbit-core</artifactId>
<version>2.0.0</version>
<scope>test</scope>
</dependency>
still results in
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='org.apache.jackrabbit:jackrabbit-core'}' and
'Vertex{label='org.apache.jackrabbit:jackrabbit-jcr-commons'}' introduces to
cycle in the graph org.apache.jackrabbit:jackrabbit-jcr-commons -->
org.apache.jackrabbit:jackrabbit-core -->
org.apache.jackrabbit:jackrabbit-jcr-commons
> Split jcr-commons in two
> -------------------------
>
> Key: JCR-2692
> URL: https://issues.apache.org/jira/browse/JCR-2692
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-commons
> Affects Versions: 2.2.0
> Reporter: Michael Dürig
>
> As discussed in JCR-2688, the jcr commons module should be split:
> * jcr-impl-commons - utility classes/interfaces for help *implementing* JCR
> * jcr-api-commons - utility classes/interfaces for help *using* JCR
> The rational is that it contains utility classes for jackrabbit-core on one
> hand and utility classes for JCR API consumers on the other hand. Currently
> there is no clean way to add unit tests for JCR API utility classes since
> this would introduce a circular dependency on jackrabbit-core. Such unit
> tests currently live in the jackrabbit-core module in the
> o.a.j.core.integration package. Along with the split these tests should be
> considered to be moved to the jcr-api-commons module.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
