You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "jira-importer (via GitHub)" <gi...@apache.org> on 2025/04/02 06:59:54 UTC
[I] [MDEPLOY-160] Deploy all installed artifacts [maven-deploy-plugin]
jira-importer opened a new issue, #216:
URL: https://github.com/apache/maven-deploy-plugin/issues/216
**[scolebourne2](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=scolebourne2)** opened **[MDEPLOY-160](https://issues.apache.org/jira/browse/MDEPLOY-160?redirect=false)** and commented
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.
---
**Affects:** 2.7
2 votes, 5 watchers
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-160] Deploy all installed artifacts [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #216:
URL: https://github.com/apache/maven-deploy-plugin/issues/216#issuecomment-2771515764
**[Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise)** commented
This is addresses to the community and whoever is concerned about it. Apart from that you have written that you critically need this..So no reaction on that for that over the last 8+ Months...so i have to suppose that it couldn't be that critical...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-160] Deploy all installed artifacts [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #216:
URL: https://github.com/apache/maven-deploy-plugin/issues/216#issuecomment-2771515754
**[Julien CARSIQUE](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jcarsique)** commented
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-160] Deploy all installed artifacts [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #216:
URL: https://github.com/apache/maven-deploy-plugin/issues/216#issuecomment-2771515773
**[林万程](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=linwancen)** commented
I also want to add a function to it. When deploying the file, we don't need to enter GAV, it will automatically read the pom file in the jar, and we can select the directory deploy all.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-160] Deploy all installed artifacts [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #216:
URL: https://github.com/apache/maven-deploy-plugin/issues/216#issuecomment-2771515767
**[Stephen Colebourne](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=scolebourne)** commented
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-160] Deploy all installed artifacts [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #216:
URL: https://github.com/apache/maven-deploy-plugin/issues/216#issuecomment-2771515757
**[Julien CARSIQUE](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jcarsique)** commented
Who is addressed the "waiting for feedback" to?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [MDEPLOY-160] Deploy all installed artifacts [maven-deploy-plugin]
Posted by "jira-importer (via GitHub)" <gi...@apache.org>.
jira-importer commented on issue #216:
URL: https://github.com/apache/maven-deploy-plugin/issues/216#issuecomment-2771515748
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented
Looks like MDEPLOY-118 to me, right?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org