kriegaex commented on PR #133: URL: https://github.com/apache/xalan-java/pull/133#issuecomment-1836452853
> > The opposite is true IMO. As we have no way to remote-debug CI, the only chance we have to identify problems there is verbose logging. Not debug level, of course, but default Maven logging. > > I split the difference. Default logging includes a lot of stuff that we really don't need to see every time (...) If the build passes, nobody will read the full log all the time anyway. If it fails, the error(s) will be towards the bottom or otherwise easily identifiable in the log. Question: Do the log lines "eat any bread", as we say in German? They do not cost us either time or local paid storage. Is there even a real problem to solve here? I consider it a luxury to have morelogs than we might need. But actually, I appreciate that the javadoc logs keep nagging use, because that incentivises us to either fix the warnings or find another way to handle the situation. I love information radiators,especially the ones I get for free. Usually the test passes, and then the green dot is all I need to know. If itfails, I am happy to get my hands on all info I can possible get. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
