码头运行旧战争alt mvn清洁运行 [英] Jetty runs old war altought mvn clean is run

问题描述

有人在maven和码头上遇到了类似的问题，尽管运行了mvn clean，但码头运行时却经历了古老的战争.

does someone had an similar issue with maven and jetty, that jetty is run with an old war althought mvn clean is run.

我的pom使用故障保护功能通过mvn验证开始跳船.

My pom uses failsafe to start jetty with mvn verify.

推荐答案

请参见 http://docs.codehaus.org/display/JETTY/Temporary+Directories 用于码头存储临时文件的位置

see http://docs.codehaus.org/display/JETTY/Temporary+Directories for where jetty store temp files

=>我建议您将Maven Jetty插件配置为对应用程序使用唯一的临时目录，以避免出现任何问题.例如:

=> 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>
...

请参见 http://docs.codehaus.org/display/JETTY/Maven + Jetty +插件

这篇关于码头运行旧战争alt mvn清洁运行的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！