We had a similar problem that we solved using a profile. We have a
default test name pattern ("_FT") that designates a test as a
functional/integration test. We include a plugin entry for
maven-surefire-plugin that runs on the integration-test phase and
includes files with that pattern. If we want to ignore those tests, we
use the profile to set the pattern to something ridiculous that would
never match. All the integration tests of that pattern are then skipped.
Here are some snippets:
<properties>
<ft_patterns>_*FT</ft_patterns>
</properties>
<profile>
<id>no_fts</id>
<activation>
<activeByDefault/>
</activation>
<properties>
<ft_patterns>_XXFTXX</ft_patterns>
</properties>
</profile>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<executions>
<execution>
<id>itest</id>
<phase>integration-test</phase>
<goals>
<goal>test</goal>
</goals>
<configuration>
<skip>false</skip>
<includes>
<include>**/*${ft_patterns}.java</include>
</includes>
</configuration>
</execution>
</executions>
</plugin>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
