[
https://issues.apache.org/jira/browse/JCR-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4610:
--------------------------------
Fix Version/s: 2.24
(was: 2.22)
(was: 2.22.0)
> Tests in jackrabbit-spi2dav are not executed by default
> -------------------------------------------------------
>
> Key: JCR-4610
> URL: https://issues.apache.org/jira/browse/JCR-4610
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-spi2dav
> Affects Versions: 2.21.2
> Reporter: Konrad Windszus
> Assignee: Manfred Baedke
> Priority: Major
> Fix For: 2.24
>
>
> The (integration) tests below
> https://github.com/apache/jackrabbit/blob/0f0807d25283b8786d800dcc41821443f43c2f82/jackrabbit-spi2dav/pom.xml#L41
> are skipped by default.
> They require a Jackrabbit Server running on localhost:8080 but this is not
> started automatically during a regular Maven Build.
> It would be good to
> # run those ITs with maven-failsafe-plugin (instead of maven-surefire-plugin)
> and rename the test classes accordingly
> # first start a Jackrabbit Server similar to how it is done in
> {{jackrabbit-jcr2dav}} and stop it accordingly after tests have been executed
> # use the same profile "integrationTests" as for the other modules
> Remark: The commons JCR test suite is checked via a DavEx client in
> {{jackrabbit-jcr2dav}} but all specific tests from
> https://github.com/apache/jackrabbit/tree/trunk/jackrabbit-spi2dav/src/test/java/org/apache/jackrabbit
> are not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
