You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Boué (JIRA)" <ji...@apache.org> on 2016/08/07 14:17:20 UTC
[jira] [Commented] (MDEPLOY-213) deploy-file replaces main artifact
of a project
[ https://issues.apache.org/jira/browse/MDEPLOY-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410952#comment-15410952 ]
Guillaume Boué commented on MDEPLOY-213:
----------------------------------------
Fixed in [r1755441|http://svn.apache.org/viewvc?view=revision&revision=1755441].
> deploy-file replaces main artifact of a project
> -----------------------------------------------
>
> Key: MDEPLOY-213
> URL: https://issues.apache.org/jira/browse/MDEPLOY-213
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy-file
> Affects Versions: 2.8.2
> Reporter: Brian Oliver
> Assignee: Guillaume Boué
> Fix For: 3.0.0
>
>
> When using the deploy-file goal in a project (not from the command-line), the specified file will replace the artifact of the current project, which may later lead to project artifact corruption, especially in a multi-module build. Instead the deploy-file goal should not touch the project artifact, or it should be conditionally set.
> The offending line should be removed from DeployFileMojo
> {code}
> //project.setArtifact( artifact );
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)