You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2010/08/03 21:56:20 UTC

[jira] Issue Comment Edited: (JCR-2692) Split jcr-commons in two

    [ https://issues.apache.org/jira/browse/JCR-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895009#action_12895009 ] 

Tobias Bocanegra edited comment on JCR-2692 at 8/3/10 3:55 PM:
---------------------------------------------------------------

can you please provide details where which class would move to?

can't we move all the "core-support" stuff to spi-commons?

otherwise: i support jukka's idea to use a released version of jackrabbit-core for testing,

      was (Author: tripod):
    can you please provide details there what class would move?

can't we move all the "core-support" stuff to spi-commons?

otherwise: i support jukka's idea to use a released version of jackrabbit-core for testing,
  
> 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.