[
https://issues.apache.org/jira/browse/MDEPLOY-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965724#comment-17965724
]
Olivier Lamy commented on MDEPLOY-124:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#333|https://github.com/apache/maven-deploy-plugin/issues/333].
> Deploy without build
> --------------------
>
> Key: MDEPLOY-124
> URL: https://issues.apache.org/jira/browse/MDEPLOY-124
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Reporter: Paul Gier
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
