[ http://jira.codehaus.org/browse/MASSEMBLY-111?page=all ]
John Casey closed MASSEMBLY-111.
--------------------------------
Assignee: John Casey
Resolution: Fixed
Fix Version/s: 2.2
This has been fixed, and the verification test is in:
src/it/dependency-sets/include-provided
The child2 project should build a jar assembly archive that contains the
child1.jar dep, even though it's marked as provided.
> Assembly has no way of including provided dependencies
> ------------------------------------------------------
>
> Key: MASSEMBLY-111
> URL: http://jira.codehaus.org/browse/MASSEMBLY-111
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Martijn Dashorst
> Assigned To: John Casey
> Fix For: 2.2
>
> Attachments: foo.zip
>
>
> When building a mixed binary/source dependency, it is not possible to include
> provided dependencies into the final assembly. scope = compile only includes
> compile time dependencies, and not provided one's.
> Adding a dependency set with scope=provided doesn't do anything.
--
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
