You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/23 11:24:00 UTC

[jira] [Commented] (MDEPLOY-124) Deploy without build

    [ https://issues.apache.org/jira/browse/MDEPLOY-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002210#comment-17002210 ] 

Elliotte Rusty Harold commented on MDEPLOY-124:
-----------------------------------------------

seems useful, but also risky. What if the artifacts change in between build and deploy? 

> Deploy without build
> --------------------
>
>                 Key: MDEPLOY-124
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-124
>             Project: Maven Deploy Plugin
>          Issue Type: New Feature
>            Reporter: Paul Gier
>            Priority: Major
>              Labels: contributers-welcome
>             Fix For: waiting-for-feedback
>
>
> We have a use case where we would like to run a build (up to the install phase) and then deploy at a later time.  Currently, the deploy plugin requires that a full build be re-run in order to deploy.  Since the build does not record the list of attached artifacts, the deploy plugin would need some way to record the list of attached artifacts, and then read them later for deployment.
> Possibly a new goal could be introduced which would create a list of attached artfiacts.  Then the deploy goal could optionally read from this list.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)