jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2055) RepositoryStub implementation in jackrabbit-core
Date Thu, 16 Apr 2009 10:53:15 GMT

    [ https://issues.apache.org/jira/browse/JCR-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699635#action_12699635

Jukka Zitting commented on JCR-2055:

> The changes introduced a compile time dependency from jackrabbit-core to jackrabbit-jcr-tests.

It's an optional dependency, so it doesn't affect downstream projects.

This change achieves a notable level of code and configuration reuse in that it avoids having
to duplicate all the test settings wherever we want to run the TCK on Jackrabbit.

If the extra optional dependency is not acceptable, we have two alternatives for keeping this
level of reuse:

1) Make a new component like "jackrabbit-test-stub" that contains the JackrabbitRepositoryStub
class and depends on both jackrabbit-core and jackrabbit-jcr-tests. IMHO we already have too
many components, so adding a new one for just a single class feels overkill.

2) Move the JackrabbitRepositoryStub class to jackrabbit-jcr-tests, with an optional dependency
to jackrabbit-core.

> RepositoryStub implementation in jackrabbit-core
> ------------------------------------------------
>                 Key: JCR-2055
>                 URL: https://issues.apache.org/jira/browse/JCR-2055
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-core, jackrabbit-spi2jcr
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.6.0
> Currently setting up a Jackrabbit repository for use with the TCK is a relatively complex
operation with a large repositoryStubImpl.properties file and lots of specially crafted test
content and settings to worry about. This makes it hard to set up new TCK test instances with
the various JCR and SPI layers we now have.
> To simplify things I'd like to introduce a RepositoryStubImpl class and related configuration
files inside src/main/java in jackrabbit-core.

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

View raw message