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-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
