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]
