jira-importer commented on issue #333: URL: https://github.com/apache/maven-deploy-plugin/issues/333#issuecomment-2771532003
**[Julien CARSIQUE](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jcarsique)** commented I made a similar suggestion on MDEPLOY-160 Taking into account Stephen's comment, I would rather - create a dedicated goal for the first step which does not actually deploy but registers what to deploy, - then a property can be used on the existing deploy goal to provide the list of artifacts to deploy. That way, in the worst case, the build would happen while not expected, or the deploy would fail because of a missing file. Using the deploy-file goal would make sense but the deploy goal could be even more relevant: allowing to browse the modules and skip the build (or not), check that the artifact previously produced is consistent with the module being processed... -- 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
