Le mar. 21 févr. 2023 à 00:13, Elliotte Rusty Harold <[email protected]> a écrit :
> On Mon, Feb 20, 2023 at 10:56 PM Romain Manni-Bucau > <[email protected]> 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. > ....until feature is a log as in maven ;) > 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. > For a download error or an artifact error you do as much as the classpath is key for the compiler plugin. There is no silver bullet so depends your case and default should guide on common errors. Current logs helped several times, are only logged on downloads (almost never on a well setup build) and we have flags to drop them at need so I'd rather chase actual issues like interleaving or optimise the "ui" like mvnd did than dropping info which has its public. That said, if we move to loggers and use --logging-xxx cli opts we can make it customizable with a user home default set of cli options which would make everyone happy as everyone is with vi and a setup per person ;). > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
