[
http://jira.codehaus.org/browse/MDEP-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MDEP-44:
--------------------------
Fix Version/s: (was: 2.0-alpha-2)
2.0-alpha-3
need to write some integration tests before this can be applied.
> unpacking/copying of attached artifacts from reactor projects doesn't work
> --------------------------------------------------------------------------
>
> Key: MDEP-44
> URL: http://jira.codehaus.org/browse/MDEP-44
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Affects Versions: 2.0-alpha-1
> Reporter: Richard van der Hoff
> Fix For: 2.0-alpha-3
>
> Attachments: dependency-issue.zip, diff.txt
>
>
> I have a parent project, which has two modules - "one" and "two".
> "one" uses assembly:single to attach an assembly to its build.
> "two" depends upon that assembly, and uses "dependency:unpack-dependencies"
> to unpack it.
> This works fine if the projects are built separately - and the assembly is
> installed in the local repository. However, when using the reactor to build
> both projects at once, the dependency plugin still looks in the local
> repository for the assembly, rather than using the artifact which was just
> built. This either fails, or produces the wrong version of the assembly.
> I suspect this may be a bug with the reactor mechanism - but I don't really
> understand how all that works...
> The attachment demonstrates the problem.
--
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
