[
https://issues.apache.org/jira/browse/MDEPLOY-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190811#comment-15190811
]
Stephen Colebourne commented on MDEPLOY-160:
--------------------------------------------
As the OP, I no longer have need of this feature as that particular project has
ended. However, I believe it is still of importance, as it allows maven to be
used in build pipelines.
Specifically, it should be possible to build and install a project in one
command, and then in a separate command, take what was installed and deploy it.
The benefit of being able to run multiple installs followed by one deploy of a
combined set of artifacts drops out naturally from this.
> Deploy all installed artifacts
> ------------------------------
>
> Key: MDEPLOY-160
> URL: https://issues.apache.org/jira/browse/MDEPLOY-160
> Project: Maven Deploy Plugin
> Issue Type: New Feature
> Affects Versions: 2.7
> Reporter: scolebourne2
> Fix For: waiting-for-feedback
>
>
> This is related to MDEPLOY-124, however it is sufficiently different to the
> discussion there to warrant a separate issue.
> I'm proposing a single new goal in the plugin, "{{deploy:installed}}". This
> new goal would deploy all the artifacts currently in the local repo as per
> the GAV in the pom. A filter set could be used to filter the list.
> This mojo should in theory be relatively simple to write. Read the list of
> files in the local repo, work out the classifiers and deploy them. Unless I'm
> missing something...
> The solution propsed in MDEPLOY-124 would not work in my use case. We have a
> build where there is a native element that is built on two (or more)
> different machines. We would like to end up with a combined deploy folder.
> ie. Linux machine produces pom, jar and linux artifacts, whereas the Windows
> machine produces pom, jar and windows artifacts. The only time there is a
> complete set of artifacts to deploy is when both machines have run and pushed
> to a shared local repo. The goal would be more generally useful than this, as
> it would allow install, test/review, deploy, workflows, which seems to be a
> pretty common desire not supported by maven.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
