Hi,
On Fri, Apr 13, 2012 at 5:43 PM, <[email protected]> wrote:
> <properties>
> <skip.deployment>true</skip.deployment>
> - <known.issues>
> + </properties>
> +
> + <build>
> + <plugins>
> + <plugin>
> + <groupId>org.apache.maven.plugins</groupId>
> + <artifactId>maven-surefire-plugin</artifactId>
> + <configuration>
> + <systemProperties>
> + <property>
> + <name>known.issues</name>
> + <value>
> org.apache.jackrabbit.test.api
> org.apache.jackrabbit.test.api.query
> org.apache.jackrabbit.test.api.query.qom
> @@ -44,9 +55,14 @@ org.apache.jackrabbit.test.api.version.s
> org.apache.jackrabbit.test.api.observation
> org.apache.jackrabbit.test.api.retention
> org.apache.jackrabbit.test.api.security
> - </known.issues>
> - </properties>
> -
> + </value>
> + </property>
> + </systemProperties>
> + </configuration>
> + </plugin>
> + </plugins>
> + </build>
The oak-parent already has Maven Failsafe plugin configuration for
this. The ${known.issues} property as defined in the <properties/>
section is automatically picked up by that configuration.
> -public class JcrTckIT extends TestCase {
> +public class JcrTckITest extends TestCase {
The Failsafe plugin uses SomethingIT instead of SomethingTest as the
test name pattern to distinguish integration tests from unit tests.
The integration tests are run when the integrationTesting profile is
used, like in: "mvn clean install -PintegrationTesting".
BR,
Jukka Zitting
