[
https://issues.apache.org/jira/browse/MDEPLOY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840460#comment-17840460
]
ASF GitHub Bot commented on MDEPLOY-314:
----------------------------------------
cstamas commented on PR #45:
URL:
https://github.com/apache/maven-deploy-plugin/pull/45#issuecomment-2075072568
merged w/ tweaks as b9c1c8bc486c7defb92171e1ea9169075b76695c
> Include artifactId in messages of DeployMojo#processProject
> -----------------------------------------------------------
>
> Key: MDEPLOY-314
> URL: https://issues.apache.org/jira/browse/MDEPLOY-314
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Components: deploy:deploy
> Affects Versions: 3.1.1
> Reporter: András Péteri
> Assignee: Tamas Cservenak
> Priority: Minor
> Fix For: 3.1.2
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
