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, 22 Aug 2011 09:22:32 GMT

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

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

I'd rather separate goals than a property. That way it is explicit what the user is requesting
(two phase versus one phase) a mojo property could be set for one module in a multi-module
build and then the user who is use to one phase deploy gets caught off-guard and never does
the second phase because they were not watching the build log like a hawk and the build did
not fail

> Deploy without build
> --------------------
>
>                 Key: MDEPLOY-124
>                 URL: https://jira.codehaus.org/browse/MDEPLOY-124
>             Project: Maven 2.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

        

Mime
View raw message