[
https://issues.apache.org/jira/browse/MDEPLOY-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965829#comment-17965829
]
Olivier Lamy commented on MDEPLOY-213:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#371|https://github.com/apache/maven-deploy-plugin/issues/371].
> deploy-file replaces main artifact of a project
> -----------------------------------------------
>
> Key: MDEPLOY-213
> URL: https://issues.apache.org/jira/browse/MDEPLOY-213
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Components: deploy:deploy-file
> Affects Versions: 2.8.2
> Reporter: Brian Oliver
> Assignee: Guillaume Boué
> Priority: Major
> Fix For: 3.0.0-M1
>
>
> 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
(v8.20.10#820010)
