But this dosn't change my situation.The failsafe plugin has to be configured in the ear module, but the test classes have to be in the webmodule. I can manualy set the path to the test files, but this has no effect. Perhaps I've forgotten something
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-failsafe-plugin</artifactId> <configuration> <testSourceDirectory>../project.web/src/test/java</testSourceDirectory> </configuration> <executions> <execution> <id>integration-test</id> <goals> <goal>integration-test</goal> </goals> </execution> <execution> <id>verify</id> <goals> <goal>verify</goal> </goals> </execution> </executions> </plugin> Am 25.10.2010 19:53, schrieb Antonio Petrelli:
2010/10/25 Dirk Reske<[email protected]>:Because a module with packaging ear, does not look for a src/test/java directory (But if, where goes the compiled classes to in the ear file).Good point :-D You can anyway configure your integration testing through the use of the failsafe plugin: http://maven.apache.org/plugins/maven-failsafe-plugin/ that focuses on integration testing and runs tests *after* packaging, in the verify phase. You can start the container in pre-integration-test phase, run tests in integration-test and stop the server in post-integration-test. Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
