No.

Ralph

> On Feb 5, 2017, at 11:50 AM, Gary Gregory (JIRA) <j...@apache.org> wrote:
> 
> 
>    [ 
> https://issues.apache.org/jira/browse/LOG4J2-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853316#comment-15853316
>  ] 
> 
> Gary Gregory commented on LOG4J2-1809:
> --------------------------------------
> 
> It seems we are entering Apache Commons Configuration territory here. Should 
> we have a bridge to it?
> 
>> Add global configuration environment SPI
>> ----------------------------------------
>> 
>>                Key: LOG4J2-1809
>>                URL: https://issues.apache.org/jira/browse/LOG4J2-1809
>>            Project: Log4j 2
>>         Issue Type: New Feature
>>         Components: API
>>           Reporter: Matt Sicker
>>           Assignee: Matt Sicker
>> 
>> Create a service provider interface for global configuration property 
>> sources. Currently, we support two built in sources: properties loaded from 
>> a classpath resource file named "log4j2.component.properties" and from 
>> system properties. This feature will abstract those two sources into an SPI 
>> with default implementations of those two sources as well as environment 
>> variables.
>> This SPI should be specified through the standard 
>> [ServiceLoader|https://docs.oracle.com/javase/8/docs/api/java/util/ServiceLoader.html]
>>  API so as to make this simpler to support for users in any environment.
>> Related to LOG4J2-1431.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Reply via email to