yes.

you need to rethink your testing... perhaps the client module is actually a test scoped dep of your war (assuming it is not a current dep of your war) in which case you run the tests in the war module

Sent from my [rhymes with tryPod] ;-)

On 16 Mar 2010, at 17:59, Filippo De Luca <[email protected]> wrote:

Hi maven users,
I have a multimodule project with one war module and a jar module. The jar
module is a client for the war module.

The server pom contains:

<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<configuration>
<scanIntervalSeconds>10</scanIntervalSeconds>
<webAppConfig>
<contextPath>/xxx-service</contextPath>
</webAppConfig>
<stopKey>stop</stopKey>
<stopPort>8009</stopPort>
</configuration>
               <executions>
<execution>
<id>start-jetty</id>
<phase>pre-integration-test</phase>
<goals>
<goal>run-exploded</goal>
</goals>
<configuration>
<scanIntervalSeconds>0</scanIntervalSeconds>
<daemon>true</daemon>
</configuration>
</execution>
<execution>
<id>stop-jetty</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop</goal>
</goals>
</execution>
               </executions>
</plugin>


The client pom contains:

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>failsafe-maven-plugin</artifactId>
<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>

When I invoke mvn integration-test on the parent project, the tests finished succesfully, while if i invoke mvn verify, the test filed because jetty has
been stopped before the client tests are invoked. Is it my error?

--
Filippo De Luca
--------------------------
Email: [email protected]
Web:   http://www.filosganga.it
LinkedIn: http://www.linkedin.com/in/filippodeluca
mobile: +393395822588

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to