[
https://issues.apache.org/jira/browse/MNG-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825180#comment-17825180
]
ASF GitHub Bot commented on MNG-8069:
-------------------------------------
gnodet commented on PR #1435:
URL: https://github.com/apache/maven/pull/1435#issuecomment-1987790899
Wouldn't it be better to add the cause when the project is banned rather
than trying to reconstruct it later ? I wonder if we should enhance the
[`blacklist()`
method](https://github.com/apache/maven/blob/0b3246381d12e69deef63888d0db274fb49c6697/maven-core/src/main/java/org/apache/maven/lifecycle/internal/ReactorBuildStatus.java#L49)
to be given a cause...
Also, what about providing two slightly different messages, I think it's
interesting to know if the project has been skipped because one project has
failed (without the fail-at-end flag, do we actually need to display the
failing projects for each skipped project, even unrelated ?) or it's actually
an upstream project which caused the failure ?
> Message "This project has been banned from the build due to previous
> failures." is too unspecific
> -------------------------------------------------------------------------------------------------
>
> Key: MNG-8069
> URL: https://issues.apache.org/jira/browse/MNG-8069
> Project: Maven
> Issue Type: Improvement
> Reporter: Christoph Läubrich
> Priority: Major
>
> Currently if a multimodule build fails (either fast or at the end), the user
> gets a message in the log that reads:
> {quote}This project has been banned from the build due to previous
> failures.{quote}
>
> this is correct but does not give a hint *what* has failed and one needs to
> investigate the build logs to get more details.
> Instead the message should show the actual project that make it impossible to
> build this and is the reason fro this project being banned.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
