does someone had an similar issue with maven and jetty, that jetty is run with an old war althought mvn clean is run.
My pom uses failsafe to start jetty with mvn verify.
does someone had an similar issue with maven and jetty, that jetty is run with an old war althought mvn clean is run.
My pom uses failsafe to start jetty with mvn verify.
see http://docs.codehaus.org/display/JETTY/Temporary+Directories for where jetty store temp files
=> I suggest you configure maven jetty plugin to use a unique temp directory for your application to avoid any problem. e.g.:
<project>
...
<plugins>
...
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<configuration>
<tmpDir>target/jetty-tmp/myApp</tmpDir>
...
see http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin