jira-importer opened a new issue, #407: URL: https://github.com/apache/maven-deploy-plugin/issues/407
**[András Péteri](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=apeteri)** opened **[MDEPLOY-314](https://issues.apache.org/jira/browse/MDEPLOY-314?redirect=false)** and commented In "deploy all at once" mode a single project does the heavy lifting for all reactor projects once it is determined that others have already been marked with an instance of the `State` enum earlier. As mentioned in a [comment](https://github.com/apache/maven-deploy-plugin/pull/39/files/327e65c5dd5e5ed92910858d4cf66ce946e22bbe#r1398970349) on PR #39, if a warning is written to the log or an exception is thrown at this point, the issue can be falsely attributed to the current project, and the real culprit can only be determined by temporarily switching back to eager deploy mode. It would be nice to display which project is being processed, making this investigation easier. --- **Affects:** 3.1.1 **Remote Links:** - [GitHub Pull Request #45 ](https://github.com/apache/maven-deploy-plugin/pull/45) -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
