|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
https://github.com/richmayfield/logback/commit/e0f4c095f188190be5d7adaa1f47310630b6e190
With this in place I can register ComponentFactory implementations as OSGi services, which avoids many configuration issues associated with adding fragments to logback in Eclipse Virgo.
The main change is in OptionHelper, which is where we get the component factory, if defined, use it, and then use the default/current mechanism as a fallback.
The ContextComponentFactory is an implementation of ComponentFactory that has the current behavior based upon the logback context.
The ClassLoaderComponentFactory can be used by any OSGi bundle to register it's own class loader.
At your convenience, please let me know what you think.