Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
2.4
-
None
-
None
-
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 13:51:
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"Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 13:51: 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"
Description
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