[mojo-dev] [jira] (MWEBSTART-268) Transitive dependencies not working when using Maven 3.1.1

[Inaki (JIRA)]

Title: Message Title

Inaki edited a comment on an issue   Re: Transitive dependencies not working when using Maven 3.1.1 Similar problem found. We solved this issue by recompiling webstart-maven-plugin with this change to the JNLPMojo: Original Code: {code:title=JNLPMojo.java|borderStyle=solid} @Mojo( name = "jnlp", defaultPhase = LifecyclePhase.PACKAGE, requiresProject = true, inheritByDefault = true,        requiresDependencyResolution = ResolutionScope.RUNTIME, aggregator = true ) @Execute( phase = LifecyclePhase.PACKAGE ) public class JnlpMojo     extends AbstractJnlpMojo {     // ----------------------------------------------------------------------     // Mojo Parameters     // ----------------------------------------------------------------------     /**      * Get the executed project from the forked lifecycle.      */     @Parameter( defaultValue = "${executedProject}", required = true, readonly = true )     private MavenProject executedProject; .... {code} Change: {panel}     @Parameter( defaultValue = " \ $ \  { *project*  \  } " , required = true, readonly = true )     private MavenProject executedProject; {panel} Explanation:    Project variable actually resolves dependencies efficiently. Add Comment   Mojo's Webstart Maven Plugin / MWEBSTART-268 Transitive dependencies not working when using Maven 3.1.1 I have the following Maven project: root - core - client - jnlp - war The client module depends on the core module. The jnlp module uses the webstart-maven-plugin plugin (jnlp-download-servlet goal.) and has a "jar-resource" reference to the client module. When I run "mvn clean install", the resulting jnlp bundle contains only the client modul... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email