[
https://issues.apache.org/jira/browse/MDEPLOY-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965715#comment-17965715
]
Olivier Lamy commented on MDEPLOY-212:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#179|https://github.com/apache/maven-deploy-plugin/issues/179].
> deploy-file incorrectly deploys attached artifacts
> --------------------------------------------------
>
> Key: MDEPLOY-212
> URL: https://issues.apache.org/jira/browse/MDEPLOY-212
> 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: Critical
> Fix For: 3.0.0-M1
>
>
> When using the deploy-file goal in a Maven pom (not from the command-line),
> the deploy-file goal will attempt to additionally deploy all attached
> artifacts, instead of the individually specified file.
> The point of the deploy-file goal is to deploy the specified artifact and
> optionally the specified source, javadoc and other classified files.
> Due to this issue it will unfortunately attempt to deploy other artifacts,
> like -test.jars that may have been generated.
> The following lines in DeployFileMojo should be conditional, perhaps based on
> a property "includeAttachedArtifacts".
> {code}
> List<Artifact> attachedArtifacts = project.getAttachedArtifacts();
> for ( Artifact attached : attachedArtifacts )
> {
> deployableArtifacts.add( attached );
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
