jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] Created: (JCR-2692) Split jcr-commons in two
Date Mon, 02 Aug 2010 17:06:21 GMT
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

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

View raw message