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 "Gary Gregory (JIRA)" <ji...@apache.org> on 2015/03/03 23:30:06 UTC
[jira] [Resolved] (LOG4J2-967) log4j2.component.properties not read
for all properties
[ https://issues.apache.org/jira/browse/LOG4J2-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Gregory resolved LOG4J2-967.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.2.1
Patch applied and pushed to Git master. Please verify and close.
> log4j2.component.properties not read for all properties
> -------------------------------------------------------
>
> Key: LOG4J2-967
> URL: https://issues.apache.org/jira/browse/LOG4J2-967
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2
> Reporter: Stefan Wehner
> Priority: Minor
> Fix For: 2.2.1
>
> Attachments: use_propertiesutils.patch
>
>
> Some parts of the code read System properties using System.getProperty and some do it through PropertyUtils. I've added a patch to read all config properties using PropertyUtils so that values specified in log4j2.component.properties will be honored.
> I guess all this'll be obsolete if LOG4J2-321 will get done, but in the meantime it'd be nice for the code to behave the same way for all properties.
--
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