maven test-plugin silently ignores test definitions in the POM when run under
maven 1.1 beta 2
----------------------------------------------------------------------------------------------
Key: MPTEST-56
URL: http://jira.codehaus.org/browse/MPTEST-56
Project: maven-test-plugin
Type: Bug
Versions: 1.7
Reporter: Henning Schmiedehausen
use the following unitTest definition in your POM:
<unitTest>
<includes>
<include>**/*Test.java</include>
</includes>
<includes>
<include>**/Test*.java</include>
</includes>
<excludes>
<exclude>**/test/*.java</exclude>
</excludes>
[...]
</unitTest>
When running under maven 1.0.2, all Test classes that start with Test or end
with Test are executed.
When running under maven 1.1-beta2, only the classes starting with Test are
executed. The second <includes> definition overrides the first. Under maven
1.0.2 the two definitions are added.
According to my understanding of the xsd, there should either be a maxOccurs to
prevent this, an exception being thrown when encountering the second includes
or the old maven 1.0.2 behaviour being restored.
This is a real world example. I ran into this when test driving the Jakarta
Turbine 2.3.2 RC1 with maven 1.1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
