multi-project modules include files from all previously processed modules
-------------------------------------------------------------------------
Key: MOJO-1020
URL: http://jira.codehaus.org/browse/MOJO-1020
Project: Mojo
Issue Type: Bug
Components: javascript-tools
Environment: java version "1.6.0_03"
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing)
Maven version: 2.0.8
Java version: 1.6.0_03
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Reporter: Harlan Iverson
Attachments: multiproject-demo.zip
When compiling several JS projects as part of a multi-project module, files
from all modules already processed are carried forward into each subsequent
module.
For example, you have a parent project and three children: lib-a, lib-b, lib-c.
The lib-a jar contains only lib-a files; the lib-b jar contains lib-b and
lib-a; and lib-c contains lib-c, lib-c and lib-a. There are no
inter-dependencies between modules, except parent/child.
Attached is a minimal scenario , please see the contents of the packaged lib-c
jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
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
