[MNG-8069] Message "This project has been banned from the build due to previous failures." is too unspecific
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 21h 11m
- Merged PRs (30d)
- 312
Description
**[Christoph Läubrich](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=laeubi)** opened **[MNG-8069](https://issues.apache.org/jira/browse/MNG-8069?redirect=false)** and commented
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.
Instead the message should show the actual project that make it impossible to build this and is the reason fro this project being banned.
---
**Remote Links:**
- [GitHub Pull Request #1435
](https://github.com/apache/maven/pull/1435)
Contributor guide
Research direction
Start by reviewing the Maven core code that emits the quoted ban message and the linked pull request #1435. Trace how a failed project is recorded during multimodule builds, then verify that the log identifies the project responsible for the ban in both fast-fail and end-of-build scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100