[jetty-dev] [jira] (JETTY-1548) Jetty plug-in doesn't see overlays when invoked fromt the top-level project

"Jan Bartel (JIRA)" <[email protected]> Mon, 15 Oct 2012 03:10:36 -0500 (CDT)
Newsgroups gmane.comp.java.jetty.general
Message-ID <949200390.11404.1350288636046.JavaMail.j2ee-jira@codehaus01.managed.contegix.com>
Jan Bartel
commented on JETTY-1548

Jetty plug-in doesn't see overlays when invoked fromt the top-level project

Hi Marco,

You're correct - when invoked from the top level of a multimodule build, the war artifact that is passed into the jetty plugin is actually the classes directory of the war artifact, not the built artifact.

In other words, the jetty-multi-web artifact is passed into the plugin as eg /home/janb/src/tmp/jetty-1548/multi-module/jetty-multi-web/target/classes and not /home/janb/.m2/repository/test/jetty-multi-web/0.0.1-SNAPSHOT/jetty-multi-web-0.0.1-SNAPSHOT.war

I guess this is because during a multimodule build, you're building all modules, including the war, up to and including the execution of the test phase, but not building the final artifact, so it can't be in the reactor.

However, when you're only executing the module that uses the jetty-maven-plugin (either by being in its directory and doing 'mvn test', or by being at the top level and doing 'mvn -pl :jetty-multi-cli') then maven will resolve the war artifact by looking in your local repo.

I can't think of anything that jetty could do to fix this, as this would seem to be the way that maven works. I'll have a look around some more documentation/ask around the maven dudes, but I can't see that much could be done about this ....

Jan

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators .

For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email