maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Connolly (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MDEPLOY-124) Deploy without build
Date Mon, 23 May 2011 11:10:22 GMT

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

Stephen Connolly commented on MDEPLOY-124:
------------------------------------------

so this would be a pair of goals, e.g.

deploy:imprint (which takes persists all the attached artifacts and I'm guessing checksums
of them for safety to a file in ${project.build.directory})

deploy:publish (which reads back in the persisted artifact file and publishes those artifacts)

> 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

        

Mime
View raw message