maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Boué (JIRA) <j...@apache.org>
Subject [jira] [Assigned] (MDEPLOY-212) deploy-file incorrectly deploys attached artifacts
Date Thu, 21 Jul 2016 22:55:20 GMT

     [ https://issues.apache.org/jira/browse/MDEPLOY-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guillaume Boué reassigned MDEPLOY-212:
--------------------------------------

    Assignee: Guillaume Boué

> 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
>            Assignee: Guillaume Boué
>            Priority: Critical
>             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)

Mime
View raw message