You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Tran (JIRA)" <ji...@codehaus.org> on 2009/12/31 02:21:55 UTC
[jira] Commented: (MDEP-212) copy goal example should use install
phase instead of package phase
[ http://jira.codehaus.org/browse/MDEP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204634#action_204634 ]
Dan Tran commented on MDEP-212:
-------------------------------
The common usage is to have maven-dependency-plugin to populate maven artifacts to be taken over by other plugin like maven-assembly-plugin
by another phase. I myself usually set it before package phase. Setting it as install phase is way too late.
So the current example is intended
> copy goal example should use install phase instead of package phase
> -------------------------------------------------------------------
>
> Key: MDEP-212
> URL: http://jira.codehaus.org/browse/MDEP-212
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Components: copy
> Affects Versions: 2.1
> Environment: any
> Reporter: D A
> Assignee: Brian Fox
> Priority: Minor
>
> The example usage shows:
> <phase>package</phase>
> <goals>
> <goal>copy</goal>
> </goals>
> This results in the artifact being copied from the repository before it is refreshed with the current working copy. Switching the phase to install resolved the issue.
> My apologies if this is as intended, but I can't think of a valid reason to every copy the outdated version during a package/install, so seems the copy goal should always come after packaging.
> Also their is an entry on the FAQ page that cites an example that is not shown and not in the page source..
--
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