[jetty-dev] [jira] (JETTY-1517) Resolve submodule artifacts in reactor builds with Maven 3
"Thomas Broyer (JIRA)" <[email protected]>
| Newsgroups | gmane.comp.java.jetty.general |
|---|---|
| Message-ID | <1585767138.1.1337555001087.JavaMail.j2ee-jira@codehaus01.managed.contegix.com> |
Thomas Broyer created JETTY-1517 Resolve submodule artifacts in reactor builds with Maven 3 Issue Type: Improvement Affects Versions: 8.1.3 Assignee: Unassigned Components: Maven Created: 20/May/12 6:02 PM Description: As an improvement on extraClasspath, the jetty-maven-plugin could resolve submodule artifacts from reactor builds, like the tomcat7-maven-plugin does [1]. In many cases, that would allow removing extraClasspath (which has to be updated each time you add/remove/rename a sibling submodule) and simply calling mvn jetty:run -pl :my-webapp -am instead. AFAICT, that was the original use-case for adding extraClasspath (see JETTY-1206 ), and Maven 3 now gives us the tools to do that more easily. For that to work, the jetty-maven-plugin would also need to automatically ignore non-war modules. [1] See http://tomcat.apache.org/maven-plugin-2.0-beta-1/run-mojo-features.html and http://svn.apache.org/repos/asf/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/DefaultClassLoaderEntriesCalculator.java (the API seems to be getProjectReferences) Project: Jetty Priority: Major Reporter: Thomas Broyer 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