When running maven-jetty-plugin as a plugin in a project pom.xml for an
integration test, all phases through test-compile are run twice because the
lifecycle is forked for the run, run-war, run-exploded and deploy-war goals.
At best this is annoying, at worst this can result in duplicate generated key
values or buildId or other failures. As with source and many many other maven
plugins, a separate goal such as run-no-fork could be provided for each goal which
would delegate to the current goal except that the lifecycle phase is not invoked
as part of the execution, i.e. like
Or provide a configuration value with <fork>true</fork> as the default for backwards compatibility, such as
with the maven-compiler-plugin. There is no workaround - the previous lifecycle
phases are either executed twice, or not at all.
Steps to Reproduce:
1. pom.xml which invokes jetty:run, i.e. as shown in
2. Run pom.xml. compile, resources phases are executed twice
3. See http://stackoverflow.com/questions/4526773/maven-jetty-plugin-question
for a specific configuration example