You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Oliver (JIRA)" <ji...@apache.org> on 2016/07/21 19:18:20 UTC
[jira] [Created] (MDEPLOY-212) deploy-file incorrectly deploys
attached artifacts
Brian Oliver created MDEPLOY-212:
------------------------------------
Summary: deploy-file incorrectly deploys attached artifacts
Key: MDEPLOY-212
URL: https://issues.apache.org/jira/browse/MDEPLOY-212
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.8.2
Reporter: Brian Oliver
Fix For: 3.0.0
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
(v6.3.4#6332)