[
https://issues.jboss.org/browse/AS7-439?page=com.atlassian.jira.plugin.sy...
]
David Bosschaert commented on AS7-439:
--------------------------------------
I have implemented this in two parts:
* I have replaced the jbosgi-common component (which embeds slf4j) with a leaner
jbosgi-logging component, which only provides the bridge from OSGi Logging to JBoss
logging, as all the other logging systems are already available in AS7. The repo is here:
https://github.com/bosschaert/jbosgi-logging and needs to be forked to jbosgi before
releasing it. I am not an admin on jbosgi so please fork for me or make me an admin so I
can do this.
* On the AS7 side I have implemented the necessary changes on this branch:
https://github.com/bosschaert/jboss-as/tree/as7_439
* Still to do: write an automated test for this in AS7, which I will do shortly.
Verify log messages from OSGi bundles feed to aggreaged logfile
---------------------------------------------------------------
Key: AS7-439
URL:
https://issues.jboss.org/browse/AS7-439
Project: Application Server 7
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: David Bosschaert
Fix For: 7.0.0.CR1
A bundle may use LogService, SLF4J, JDK, Apache Commons or JBoss Logging. All of these
must feed to the common log system
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira