[
https://issues.apache.org/jira/browse/MNG-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447524#comment-17447524
]
Guillaume Nodet edited comment on MNG-7342 at 11/22/21, 4:39 PM:
-----------------------------------------------------------------
Then I would suggest overwriting Sisu logger with a maven custom one.
The problem is not really the fact that sisu logger can be configured using
system properties but rather the fact that such exceptions are only displayed
at TRACE level, so they are completely hidden, even when using {{{}-X{}}}. So
I'd suggest logging those exceptions at DEBUG rather than TRACE level.
The problem is that even when using {{{}-X{}}}, you have no way to know what
happens at all. I had to debug and put a breakpoint inside Sisu to actually
see that I could use a system property to force Sisu to log those statements.
An alternative would be to add a {{-XX}} option to enable TRACE logging.
was (Author: gnt):
Then I would suggest overwriting Sisu logger with a maven custom one.
The problem is not really the fact that sisu logger can be configured using
system properties but rather the fact that such exceptions are only displayed
at TRACE level, so they are completely hidden, even when using `-X`. So I'd
suggest logging those exceptions at DEBUG rather than TRACE level.
> When loading plexus components, linkage exceptions are not displayed
> --------------------------------------------------------------------
>
> Key: MNG-7342
> URL: https://issues.apache.org/jira/browse/MNG-7342
> Project: Maven
> Issue Type: Bug
> Reporter: Guillaume Nodet
> Priority: Major
>
> If a dependency is missing, a {{NoClassDefFoundError}} will be thrown inside
> Sisu, but Sisu logs at {{TRACE}} level and not {{DEBUG}} so that nothing is
> displayed.
> The {{-X}} option should use {{TRACE}} instead of {{{}DEBUG{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
