Dependency missing in assembled archive in multi-project build for certain
scope combination
--------------------------------------------------------------------------------------------
Key: MASSEMBLY-568
URL: https://jira.codehaus.org/browse/MASSEMBLY-568
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2.1, 2.2
Environment: maven 3.0.3, mac osx or windows 7
Reporter: Stefan Leistenschneider
Given a multi module build parent project with module A, module B and module C.
Module C is used just for the assembly of module A. Module A depends on module
B.
Module A has a dependancy X set to scope compile, module B has the same
dependancy X set to scope test.
It is expected, that because dependancy X is set to scope compile in module A,
that the dependancy is included in the final archive, no matter what scope the
same dependency has in module B.
When assembling, dependancy X is missing in the final archive.
When setting the scope of the dependancy in module B to compile, dependancy X
is included.
Building the same project with 2.2 beta 5 and having the assembly directly in
the parent project (so without module c) works.
Building the same project with 2.2.1 or 2.2 and having the assembly directly in
the parent project does not work.
Best regards,
Stefan
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
