[
https://issues.apache.org/jira/browse/JCR-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611180#action_12611180
]
angela commented on JCR-1629:
-----------------------------
> Using the jackrabbit-jcr2spi test for a specific spi implementation is
> problematic since it has dependencies on the
> existing spi implementations (i.e. spi2jcr). What we need here is a way to
> run the jackrabbit-jcr2spi tests for an arbitrary
> spi implementation without introducing alien dependencies.
agreed. but this is yet another issue or at least an extension to the original
goal of this issue.
anyway. i will attach patches that attempt to provide
- basic setup that allows to write tests against the SPI interfaces (located in
the jackrabbit-spi project)
- clean jcr2spi from dependency to jackrabbit-spi2jcr and jackrabbit-core
- add test-jar goal for both
> jackrabbit-jcr2spi and
> jackrabbit-spi
- jackrabbit-spi2jcr: run jcr2spi-tests and spi-tests by adding extra
dependencies with the 'tests' classifier.
it worked for me (this time)... but i'm not totally convinced that this part of
the maven functionality really works reliably.
please comment
angela
> SPI: Testsuite for the SPI Interfaces
> -------------------------------------
>
> Key: JCR-1629
> URL: https://issues.apache.org/jira/browse/JCR-1629
> Project: Jackrabbit
> Issue Type: New Feature
> Components: jackrabbit-spi
> Reporter: angela
> Attachments: JCR-1629.diff
>
>
> now that people start writing SPI implementations we should provide a
> test-suite that runs on the SPI directly in order to provide the developers a
> way to assert basic compliance of their implementation without having the JCR
> api in between.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
