[
https://issues.jboss.org/browse/WELD-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611196#comment-12611196
]
Pete Muir commented on WELD-928:
--------------------------------
I really don't think this is the right solution. A developer should expect to
enable DEBUG messages in order to debug their app - and a lot of these messages
can just be ignored. If we move these up to a higher level there will be a lot
of false positives.
It would be better to move these to a new category I think - this would allow
finer grained control and would allow the AS to enable them by default should
it wish.
> Weld should log failure to load a class at a higher level than DEBUG
> --------------------------------------------------------------------
>
> Key: WELD-928
> URL: https://issues.jboss.org/browse/WELD-928
> Project: Weld
> Issue Type: Bug
> Affects Versions: 1.1.1.Final
> Reporter: Stuart Douglas
> Priority: Critical
> Fix For: 1.1.2.Final
>
>
> At the moment weld logs failure to load a class at a log level of debug,
> which is not displayed by default.
> Due to the new modular class loading in AS7 these types of errors will become
> much more frequent, and the user is given no debug information to determine
> where the problem is. Changing the default log level to DEBUG for
> org.jboss.weld.Bootstrap is not an option as this is to verbose.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues