Jesse,
I was trying to use <excludes> to exclude tests from compiling when
converting my project from m1 to m2. The <excludes> only affect what is
executed, not compiled.
Paul Spencer
Jesse McConnell wrote:
I was just poking through this code...and it was excluding all the right
stuff for me :/
so for this setup below, you want all test cases that end in
TestCase.javaexcept for those in the com/foo/util directory...right?
and this is in
src/test/java...
this doesn't add to the existing patterns to find tests, if you specify
includes and excludes those are the only patterns used to find/exclude tests
jesse
On 11/22/05, Paul Spencer <[EMAIL PROTECTED]> wrote:
The surefire plugin is not honoring the <excludes>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<fork>true</fork>
<includes>
<include>**/*TestCase.java</include>
</includes>
<excludes>
<exclude implementation="java.lang.String">
com/foo/util/**
</exclude>
</excludes>
</configuration>
</plugin>
o The <exclude> is the same one used for the maven-compiler-plugin.
o mvn -X does not list the exclusion of the test source, just the source
[DEBUG] (f) excludes = [com/foo/util/**]
Paul Spencer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
jesse mcconnell
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
