[
http://jira.codehaus.org/browse/MDEPLOY-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268171#action_268171
]
Wendy Smoak commented on MDEPLOY-124:
-------------------------------------
It sounds like the release staging feature of one of the various artifact
repositories would be useful here.
You deploy to one place, do whatever, and then promote the release later.
> Deploy without build
> --------------------
>
> Key: MDEPLOY-124
> URL: http://jira.codehaus.org/browse/MDEPLOY-124
> Project: Maven 2.x Deploy Plugin
> Issue Type: New Feature
> Reporter: Paul Gier
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
