gnodet commented on pull request #619: URL: https://github.com/apache/maven/pull/619#issuecomment-977911831
> From [sisu doco](https://www.eclipse.org/sisu/docs/tutorials/index.html#go): "If you're interested in what Sisu is doing you can turn on tracing with -Dsisu.debug" Again, the problem is not to find a way to raise sisu log. The problem was to actually find what the problem was. I had no idea that the problem came from sisu at all and I could not imagine that a NoClassDefFoundError was simply logged at _trace_ level. Trace is not meant to display exceptions, but rather very fine grained info. Such problems should at least be logged at _debug_ level, hence appearing with the standard `-X` option. Anything useful should at least happen here. I also faced a problem recently where an extension was not working in some environment. I kinda abandoned debugging it (because debugging was not possible), but I now suspect that it was the same kind of issue which was not printed at debug level. I do agree we have tons of ways to raise specific loggers level. The goal here is to have a simple option that will at least display possible problems without having to know which log level you need to raise or even that you need to raise one. Any suggestion that provides such a workaround relies on the user understanding where the problem is, which is what I'm trying to help him finding. -- 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]
