maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Mccall (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MDEP-291) Error when copying within reactor for phases earlier than package
Date Fri, 10 Dec 2010 11:01:58 GMT

    [ http://jira.codehaus.org/browse/MDEP-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247160#action_247160
] 

Sam Mccall commented on MDEP-291:
---------------------------------

A similar problem exists for dependency:copy.

Project P aggregates modules A and B. A depends on B, and A uses dependency:copy targeting
B.
When running 'mvn package' on P:
  * B will be built first (correct)
  * A will try to copy B from the repository, rather than the reactor.

Thus either A gets an old and potentially stale copy of B, or we get an error "Unable to find
artifact" during dependency:copy.

(Please let me know if I should file this as a new bug - I don't know the internals but it
looks like the same thing to me)

> Error when copying within reactor for phases earlier than package
> -----------------------------------------------------------------
>
>                 Key: MDEP-291
>                 URL: http://jira.codehaus.org/browse/MDEP-291
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>          Components: copy-dependencies
>    Affects Versions: 2.1
>         Environment: MacOS 10.6.4 (also seen on Windows XP)
> Maven 3.0
> Mac Java 1.6 (also seen on SUN JDK 1.6.0_18 on Windows)
>            Reporter: Anders Hammar
>            Assignee: Brian Fox
>         Attachments: issue-parent.zip
>
>
> For a multi-module project where a module executes dependency:copy-dependencies on another
module in the build, this does not work when building within the reactor (i.e. executing a
phase earlier than package).
> This can be recreated with the attached project:
> In the aggregating project, execute "mvn prepare-package".

-- 
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

        

Mime
View raw message