You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/05/05 16:18:30 UTC
[jira] Resolved: (JCR-2096) Move jcr2spi tests to spi2jcr
[ https://issues.apache.org/jira/browse/JCR-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-2096.
--------------------------------
Resolution: Won't Fix
Agreed. Resolving as Won't Fix.
> Move jcr2spi tests to spi2jcr
> -----------------------------
>
> Key: JCR-2096
> URL: https://issues.apache.org/jira/browse/JCR-2096
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr2spi, jackrabbit-spi2jcr, test
> Reporter: Jukka Zitting
>
> Currently we have a number of test cases included in the jcr2spi component, but they aren't being run in there (surefire plugin is disabled). Instead, the tests are packaged into a -tests jar that is then used in the spi2jcr component to run them.
> The downside of this setup are 1) extra complexity and 2) the fact that a -Dmaven.test.skip=true build will not work with a clean Maven repository as the jcr2spi -tests jar is not being built for spi2jcr.
> How about if we simply moved the tests to the spi2jcr component where they are being used?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.