You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2012/08/19 19:52:37 UTC
[jira] [Resolved] (LOG4J2-67) Allow plugins outside of Log4j 2 core
to be preloaded.
[ https://issues.apache.org/jira/browse/LOG4J2-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-67.
-------------------------------
Resolution: Fixed
Enhancement added to 2.0-alpha2
> Allow plugins outside of Log4j 2 core to be preloaded.
> ------------------------------------------------------
>
> Key: LOG4J2-67
> URL: https://issues.apache.org/jira/browse/LOG4J2-67
> Project: Log4j 2
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.0-alpha1
> Reporter: Ralph Goers
> Assignee: Ralph Goers
> Fix For: 2.0-alpha2
>
>
> Loading plugins in Log4j 2 core is fast and easy because they have been added to the preload map. However, the FlumeNG appender and components in other packages must be loaded at runtime. This enhancement should allow any component to contain a preload map and all of them should be loaded together.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org