You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2011/08/22 10:57:32 UTC

[jira] Commented: (MDEPLOY-126) Deploy only artifacts which have been explicitly attached

    [ https://jira.codehaus.org/browse/MDEPLOY-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276648#comment-276648 ] 

Stephen Connolly commented on MDEPLOY-126:
------------------------------------------

MDEPLOY-114 or MDEPLOY-117 would seem to be a more correct and less hacky solution.

Tempted to close in favour of one of those

> Deploy only artifacts which have been explicitly attached
> ---------------------------------------------------------
>
>                 Key: MDEPLOY-126
>                 URL: https://jira.codehaus.org/browse/MDEPLOY-126
>             Project: Maven 2.x Deploy Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.5
>         Environment: Maven 3
>            Reporter: Matthias Vach
>              Labels: scrub-review-started
>         Attachments: 001.diff
>
>
> Hi all,
> General Information:
> --------------------
> while releasing maven projects we do generate release metadata for any project. The generated metadate need to be uploaded to nexus and are located right beside the build results.
> Since we don't want to affect the release build iselfe, the whole metadata generation runs as a second build after the release build finished.
> Now the problem:
> --------------------
> We want to use the deploy plugin to deploy the generated release metadata to nexus. But the deploy plugin is currently attaching project artifacts and pom-files automatically to the deployment. But this causes a HTTP-400 Error at Nexus, since all pom-files and project artifacts have been deployed to Nexus already. And redeployment is not allowed.
> Currently missing:
> --------------------
> It would be cool if the deploy plugin would offer a switch to reduce the deployment only to those artifacts/files which have been explicitly attached for deployment in the reactor before.
> Attached you do find a small patch.
> Regards Matthias

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira