[
https://issues.jboss.org/browse/JBOSGI-530?page=com.atlassian.jira.plugin...
]
Thomas Diesler edited comment on JBOSGI-530 at 3/8/12 9:55 AM:
---------------------------------------------------------------
Fixed in framework-1.2.0
{code}
// Setup the logging system for jboss-modules
ModuleLogger logger = (ModuleLogger) getProperty(ModuleLogger.class.getName());
if (logger == null) {
Module.setModuleLogger(new JDKModuleLogger());
}
{code}
was (Author: thomas.diesler):
Done
// Setup the logging system for jboss-modules
ModuleLogger logger = (ModuleLogger) getProperty(ModuleLogger.class.getName());
if (logger == null) {
Module.setModuleLogger(new JDKModuleLogger());
}
No logging messages from org.jboss.modules
------------------------------------------
Key: JBOSGI-530
URL:
https://issues.jboss.org/browse/JBOSGI-530
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.1.2
jboss-modules requires the client to explicitly set the ModuleLogger, otherwise there are
no logging messages. Currently the framework does not do that
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira