On Mon, Feb 20, 2023 at 10:56 PM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > > Do you want to make maven output only SUCCESS or FAILURE? All default info > logs are close to these download logs in practise. >
Not always, but it should be far less verbose than it is now. It is an oft forgotten principle of TDD that passing tests generate no output. Maven fails that badly. Failures should indeed generate more output. However, the only helpful output is the output that points to the actual failure. Page after page of repetitive log junk only serves to obscure the true cause. It is not merely unhelpful. It actively hinders devs from finding problems. For example, a compile error should be reported with a clear message and the line, column, and file where the failure occurred. The message should be clear and actionable. But when I'm trying to figure out where a missing semicolon is, I really do not need to know every last artifact Maven downloaded, how big it is, and how long it took to download. I certainly don't need to get that information twice per artifact. -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org