[
https://issues.jboss.org/browse/JBIDE-8706?page=com.atlassian.jira.plugin...
]
Dan Florian resolved JBIDE-8706.
--------------------------------
Release Notes Text: SLF4J trace level logging can be enabled by running application
with "-debug" and referencing a ".options" file with the ModeShape
Tools plugin's "/debug" property set to "true."
Resolution: Done
Eclipse log levels of error, warn, and info can be filtered out of the Error View by using
the view's setting in its "Filter's" menu. SLF4J trace level logging can
be enabled by running application with "-debug" and referencing a
".options" file with the ModeShape Tools plugin's "/debug"
property set to "true."
Logging Of the SLF4J ModeShape Logging Does Not Adhere To Eclipse Log
Levels
----------------------------------------------------------------------------
Key: JBIDE-8706
URL:
https://issues.jboss.org/browse/JBIDE-8706
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: modeshape
Affects Versions: 3.2.0.Final
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 3.2.1
ModeShape Tools has a dependency to a ModeShape client library. This library uses SLF4J
for its logging and depends on an SLF4J logger implementation to be available at runtime.
ModeShape Tools has implemented a logger that will redirect the ModeShape logging to the
Eclipse logger. Problem is that all levels of logging are always being logged regardless
of the logging level of the running Eclipse. So lots of trace-level messages are appearing
in the Eclipse log. Another problem is that Eclipse does not have trace-level logging.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira