On Sun, Jan 29, 2023 at 10:02 AM Gary D. Gregory <ggreg...@apache.org> wrote: > > Hi Mukul, > > Thank you for working on another RC! > > In general, our build commands still output way too much information by > default IMO. The build should be quiet and tell me when things go wrong IMO, > sure some progress information is OK but I don't care that each .xsl file has > passed its test for example. WDYT? >
You are absolutely right. This is a general failure mode of most (all?) build tools. An early principle of test driven development that tool vendors have either forgotten or never learned in the first place is that passing tests generate no output. Beyond simply test output, you are also correct that most tools spam logs with junk no one wants, no one will read, and simply obscure the rare piece of useful information. Anything that can be done to improve this situation is valuable, but it's a long slog. A lot of it needs to happen in repos where maintainers are way too invested in their own tool to consider that actual users simply don't care to know what's going on in each and every method in their tool. That reminds me. I'm overdue to put some more effort into fixing this problem in Maven, though I'm afraid that won't help with Xalan's ant build. -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
