[
https://issues.apache.org/jira/browse/LOG4J2-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Weiglhofer updated LOG4J2-400:
-------------------------------------
Labels: Appender Core Dependency OSGi PluginManager lightweight optional
(was: )
> Provide Appender-Bundles
> ------------------------
>
> Key: LOG4J2-400
> URL: https://issues.apache.org/jira/browse/LOG4J2-400
> Project: Log4j 2
> Issue Type: Improvement
> Components: Appenders, Core
> Affects Versions: 2.0-beta9
> Environment: OSGi R4 / R5 (Apache Felix 4.x)
> Reporter: Roland Weiglhofer
> Priority: Critical
> Labels: Appender, Core, Dependency, OSGi, PluginManager,
> lightweight, optional
>
> Instead of deploying all appenders in the core fragment, it would be much
> better if the customer can choose which appender he wants to provide. It's
> easy to hive the appender off in a separate bundle fragment. The host bundle
> is the API bundle. The Plugin Manager (core fragment) finds the deployed
> appenders in the classpath of the host bundle. The PluginManager should parse
> the class path in a separate thread (Startup-Hook) and only once at the start
> of the host bundle, but not for each call (when a consumer bundle aquires a
> logger). Make package-imports optional
> (<Import-Package>*;resolution:=optional</Import-Package>)!!!!
> This reduces the number of dependencies and reduces the startup time of the
> whole system.
> referes to LOG4J2-389 https://issues.apache.org/jira/browse/LOG4J2-389
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
