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 "Matt Sicker (JIRA)" <ji...@apache.org> on 2015/10/31 08:20:27 UTC
[jira] [Updated] (LOG4J2-1186) Log4j component properties file not
loaded from other bundles
[ https://issues.apache.org/jira/browse/LOG4J2-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Sicker updated LOG4J2-1186:
--------------------------------
Description: In PropertiesUtil, the main Log4j properties is loaded right away. If a bundle containing log4j2.component.properties is loaded after log4j-api (which would normally be the case), then this file will be ignored. The Activator class can be used to update the main PropertiesUtil instance when new bundles are added. (was: In PropertiesUtil, the main Log4j properties is loaded right away. If a bundle containing log4j.component.properties is loaded after log4j-api (which would normally be the case), then this file will be ignored. The Activator class can be used to update the main PropertiesUtil instance when new bundles are added.)
> Log4j component properties file not loaded from other bundles
> -------------------------------------------------------------
>
> Key: LOG4J2-1186
> URL: https://issues.apache.org/jira/browse/LOG4J2-1186
> Project: Log4j 2
> Issue Type: Bug
> Components: API
> Affects Versions: 2.4.1
> Reporter: Matt Sicker
> Labels: OSGi
>
> In PropertiesUtil, the main Log4j properties is loaded right away. If a bundle containing log4j2.component.properties is loaded after log4j-api (which would normally be the case), then this file will be ignored. The Activator class can be used to update the main PropertiesUtil instance when new bundles are added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org