Brett,
1) The current behavior allows abstract test classes to be compiled but
   NOT executed, which is good.  I currently use this functionality
   on other projects.

2) The exclude list form the compiler plugin is not honored by the
   surefire plugin relative compilation of the test source.  In my
   case the exclude list of the compiler plugin was the same as the
   exclude list for the surefire plugin.  All things considered, I am
   not sure if the surefire plugin should inherit the compiler's exclude
   list.

3) Is their a different compiler plugin used by surefire?
   If yes, this what how is it addressed, i.e. artifactId?
   I have verified that the compiler configuration tags, like <source>
   and <target> in the surefire plugin configuration are not passed
   to the compiler plugin.  To me, this is a very minor issue.  I
   just mentioned it to pass along what I have learned.

Paul Spencer

Brett Porter wrote:
I've noticed this recently too. You can exclude sources from
compilation in the compiler plugin (check the compiler plugin
reference for the configuration item name).

Cheers,
Brett

On 11/23/05, Paul Spencer <[EMAIL PROTECTED]> wrote:

I should further clarify "not honoring the <excludes>".  My expectation
was the exclusion applied to the compiler and test runner.  It appear to
apply to only the test runner.
So, is it correct the excluded test are compiled and not run?

Is their a way to prevent a the compilation?

Paul Spencer

Paul Spencer 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]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to