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

Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2011/08/22 16:26:32 UTC

[jira] Issue Comment Edited: (MDEPLOY-124) Deploy without build

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

Paul Gier edited comment on MDEPLOY-124 at 8/22/11 9:26 AM:
------------------------------------------------------------

I agree it should be a separate goal, however it also needs some way to determine which files to deploy.  My previous suggestion was to add property to the existing deploy go which only creates a list of files to deploy instead of actually deploying them.  Then the second goal reads the list and deploys the files.  Another option is to just manually configure the list of files to deploy in the plugin.  Maybe this could be done as an enhancement to the existing deploy-file goal.


      was (Author: pgier):
    I agree it should be a separate goal, however it also needs some way to determine which files to deploy.  My previous suggestion was to add property to the existing deploy go which only creates a list of files to deploy instead of actually deploying them.  Then the second goal reads the list and deploys the files.  Another option is to just manually configure the list of files to deploy in the plugin.

  
> Deploy without build
> --------------------
>
>                 Key: MDEPLOY-124
>                 URL: https://jira.codehaus.org/browse/MDEPLOY-124
>             Project: Maven 2.x and 3.x Deploy Plugin
>          Issue Type: New Feature
>            Reporter: Paul Gier
>              Labels: contributers-welcome
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira