[
https://issues.apache.org/jira/browse/MNG-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824034#comment-17824034
]
ASF GitHub Bot commented on MNG-8069:
-------------------------------------
laeubi opened a new pull request, #1435:
URL: https://github.com/apache/maven/pull/1435
Currently if a multimodule build fails (either fast or at the end), the user
gets a message in the log that reads:
"This project has been banned from the build due to previous failures."
this is correct but does not give a hint what has failed and one needs to
investigate the build logs to get more details.
This now instead shows as part of the message the actual project that make
it impossible to build this one and is the reason for this project being
banned.
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MNG-8069) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
- [x] Format the pull request title like `[MNG-XXX] SUMMARY`,
where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA
issue.
- [x] Also format the first line of the commit message like `[MNG-XXX]
SUMMARY`.
Best practice is to use the JIRA issue title in both the pull request
title and in the first line of the commit message.
- [x] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [ ] You have run the [Core IT][core-its] successfully.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [ ] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
[core-its]: https://maven.apache.org/core-its/core-it-suite/
> 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)
