laeubi commented on PR #1435: URL: https://github.com/apache/maven/pull/1435#issuecomment-1987801822
The problem is that if you have a multimodule build (lets say 300 modules) and use multithreading (so build messages are interleaved), and one of the projects fail in the middle you have a huge logfile full of "banned" messages but you need to find out what/where it actually fails, so the message without any context is quite useless and even if you find the erroneous project its not very helpful. So I though showing it at tat time might be more useful. Another approach would be to simply not display the message at all, and instead give a summary at the end of build, e.g. ``` The following projects where not build due to previous failures: - a (depends on x that failed) - b - c (depends on b that was banned) ``` sadly currently this information is somehow spread across some places and I'm not sure why e.g. a listener was used instead of printing the message directly on `blacklist()` ... regarding `fae`/`ff` I think we can add such message of course but I didn't wanted to complicate things for a first draft, if you think its usefull I think it is quite easy to add, -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
