[
http://jira.codehaus.org/browse/MASSEMBLY-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183263#action_183263
]
Brian Fox commented on MASSEMBLY-432:
-------------------------------------
I saw some weird things happening in the debug logs, that make me wonder if
core isn't somehow the culprit. I did see the same behavior with 2.0.10 and
2.2.0 though. (only rebuilding the child, the parent was already deployed)
> assembly misapplies depMgt and selects the wrong dependency for an archive
> --------------------------------------------------------------------------
>
> Key: MASSEMBLY-432
> URL: http://jira.codehaus.org/browse/MASSEMBLY-432
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-3
> Reporter: Brian Fox
> Assignee: John Casey
> Attachments: assemblybug.zip
>
>
> Here's the setup:
> Parent has a depMgt set to version 1.3.4
> Child has a dependency on 1.3.5
> Assembly descriptor includes this dependency and 1.3.4 is bundled in, not
> 1.3.5.
> See attached project for a working example. First install the parent, second
> run package on the child. See the zip contains 1.3.4 instead of 1.3.5.
> Note: The real project where this happened has a property in the depMgt, if
> you use 2.0.10 this bug seems to not occur because the version is not
> interpolated in the pom that gets deployed. In 2.2 it is and causes this to
> manifest in the way I set it up, but fixing the version in the depMgt instead
> of using the property.
--
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
