You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kohsuke Kawaguchi (JIRA)" <ji...@codehaus.org> on 2007/01/07 03:58:10 UTC
[jira] Updated: (MDEP-44) unpacking/copying of attached artifacts
from reactor projects doesn't work
[ http://jira.codehaus.org/browse/MDEP-44?page=all ]
Kohsuke Kawaguchi updated MDEP-44:
----------------------------------
Attachment: diff.txt
The root cause of the problem is in the maven-project module.
Normally, the dependency resolution in Maven consults artifacts in dependency projects, so that the artifacts from earlier modules can be picked up by later modules. But this code has a bug in it that it only checks for the main artifact of modules, and not their attached artifacts.
Because of this, successive modules will fail to resolve attached artifacts from earlier modules.
The attached patch is against maven-project 2.0.4. You can rebuild the maven-project 2.0.4 with this patch, and put that in $M2_HOME/lib.
> 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
> 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