[jira] [Commented] (MDEPLOY-160) Deploy all installed artifacts

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

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

Julien CARSIQUE commented on MDEPLOY-160:
-----------------------------------------

I don't think so:
- MDEPLOY-160 is a generic and clear feature: do not rebuild already built artifacts, take them from the local repository. On implementation side, that can rely on maven-install-plugin (looking at the m2repo given the current GAV) or on maven-deploy-plugin with a specific "two steps" command or option (first execution only reminds the installed artifacts, second execution deploys those artifacts).
- MDEPLOY-118 mixes multiple issues and specific cases: POM being deployed twice, adding an alternate artifact (classifier) along with an already deployed artifact, need to define generic classifier use cases...

You can set MDEPLOY-118 as depending on MDEPLOY-160.

For advanced releasing process purpose in my company (https://jira.nuxeo.com/browse/NXBT-739), I critically need specifically MDEPLOY-124, MDEPLOY-160, MDEPLOY-169 and/or MDEPLOY-172. Whereas when I encountered MDEPLOY-118, I could more easily work around.

> Deploy all installed artifacts
> ------------------------------
>
>                 Key: MDEPLOY-160
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-160
>             Project: Maven Deploy Plugin
>          Issue Type: Bug
>    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)