diff --git a/test/plugin.jelly b/test/plugin.jelly index 5e29aae9..92f20e77 100644 --- a/test/plugin.jelly +++ b/test/plugin.jelly @@ -20,6 +20,11 @@ description="Compile the TestCases and TestSuites" prereqs="java:compile,java:jar-resources,test:prepare-filesystem,test:test-resources"> + + + + + + ${maven.junit.sysproperties} @@ -104,7 +110,7 @@ - + @@ -241,6 +247,8 @@ classname="org.apache.tools.ant.taskdefs.optional.junit.JUnitTask" /> + Searching directory ${maven.test.searchdir} + - - + + diff --git a/test/xdocs/changes.xml b/test/xdocs/changes.xml index 3437948e..dd7956f9 100644 --- a/test/xdocs/changes.xml +++ b/test/xdocs/changes.xml @@ -6,6 +6,16 @@ + + + You can now specify whether the source (java) or classes (class) files + are searched when using the test plugin via the property: + maven.test.search.classdir. It defaults to use (java) to preserve + backwards compatibilty. Using (class) allows you to work with alternative + languages that compile to bytecode like + Check if unitTest tag is present in pom before copy resources. diff --git a/test/xdocs/properties.xml b/test/xdocs/properties.xml index b457cc8d..f5bc29c8 100644 --- a/test/xdocs/properties.xml +++ b/test/xdocs/properties.xml @@ -177,6 +177,20 @@ basedir=${basedir} + + maven.test.search.classdir + Yes + + Use this property to specify that JUnit should search the test classes directory + rather than the source directory. This allows for test cases to be written in other + languages such as Groovy which generate bytecode that can then be used by this plugin. + Sample : + + + +