[
http://jira.codehaus.org/browse/MASSEMBLY-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105797
]
Daniel Siegmann commented on MASSEMBLY-236:
-------------------------------------------
In the test case from MASSEMBLY-235, we are included just three jars from a
dependency set. This set did not include xmlenc, yet that dependency must have
been resolved (since the resolution failed). There was no reason to be
resolving the dependency in this case.
I don't think I should've filed this as a bug, since it's not wrong
necessarily. However, MASSEMBLY-235 wouldn't have been exposed in my test case
if only the included dependencies were resolved. Probably this is not very
important anyway (except that it allowed MASSEMBLY-235 to be exposed).
Sorry for the lack of clarity.
> assembly:assembly resolves excluded artifacts
> ---------------------------------------------
>
> Key: MASSEMBLY-236
> URL: http://jira.codehaus.org/browse/MASSEMBLY-236
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Reporter: Daniel Siegmann
> Priority: Minor
> Fix For: 2.2-beta-2
>
>
> When creating an assembly, excluded dependencies are still resolved. If the
> artifact can't be resolved, the assembly fails, even though this artifact
> should be excluded.
> This behavior can be seen in the test project attached to issue MASSEMBLY-235.
--
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
