maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robin Roos (JIRA)" <>
Subject [jira] (MASSEMBLY-658) Assembly fails for multi-module project if webstart-maven-plugin is in use
Date Mon, 08 Jul 2013 14:53:05 GMT


Robin Roos updated MASSEMBLY-658:

    Attachment: output.log

Log output
> Assembly fails for multi-module project if webstart-maven-plugin is in use
> --------------------------------------------------------------------------
>                 Key: MASSEMBLY-658
>                 URL:
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>          Components: dependencySet
>    Affects Versions: 2.4
>         Environment: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
> 28+0000) 
> Maven home: C:\dev\apache-maven-3.0.5\bin\.. 
> Java version: 1.6.0_45, vendor: Sun Microsystems Inc. 
> Java home: C:\Program Files\Java\jdk1.6.0_45\jre 
> Default locale: en_GB, platform encoding: Cp1252 
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>            Reporter: Robin Roos
>         Attachments:, output.log
> The mvn invocation I used is:
> mvn clean package
> I attach a simple test case of a multi-module project. If the acme-jnlp module is commented
out in the parent POM then the project builds successfully. If the acme-jnlp module is not
commented out, then the assembly of acme-dist fails because of a NullPointerException.
> acme-dist and acme-war to not rely on the artifacts generated by acme-jnlp. The mere
fact that the plugin is executed causes the later module assembly to fail.
> Modules have the following purposes:
> acme-parent: parent project which contains the module
> acme-jnlp: create JNLP and ZIP files not used by any other modules
> acme-war: create a .WAR file
> acme-dist: use assembly plugin to create a .ZIP containing the .WAR
> acme-deploy: holds dependencies to other modules, but does nothing else

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:

View raw message