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

["Julien CARSIQUE (JIRA)" <ji...@apache.org>]

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

Julien CARSIQUE commented on MDEPLOY-124:
-----------------------------------------

I made a similar suggestion on MDEPLOY-160
Taking into account Stephen's comment, I would rather
- create a dedicated goal for the first step which does not actually deploy but registers what to deploy,
- then a property can be used on the existing deploy goal to provide the list of artifacts to deploy. That way, in the worst case, the build would happen while not expected, or the deploy would fail because of a missing file.
Using the deploy-file goal would make sense but the deploy goal could be even more relevant: allowing to browse the modules and skip the build (or not), check that the artifact previously produced is consistent with the module being processed...

> 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
>              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
(v6.3.4#6332)