[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

2017-02-05 Thread Matt Sicker (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853384#comment-15853384
 ] 

Matt Sicker commented on LOG4J2-1431:
-

Thankfully, parsing the property names turned out to be a lot simpler than 
initially expected thanks to some regular expressions. This feature is pretty 
much code complete in the LOG4J2-1431 branch. I'd still like to update the 
manual to reference the normalized property names instead of the mish-mash we 
have currently. Here are some random examples of updates:

* log4j2.AsyncQueueFullPolicy -> log4j2.asyncQueueFullPolicy
* log4j.configurationFile -> log4j2.configurationFile
* AsyncLogger.ExceptionHandler -> log4j2.asyncLoggerExceptionHandler
* Log4jContextSelector -> log4j2.contextSelector

> Simplify log4j system property naming scheme
> 
>
> Key: LOG4J2-1431
> URL: https://issues.apache.org/jira/browse/LOG4J2-1431
> Project: Log4j 2
>  Issue Type: Improvement
>Reporter: Matt Sicker
>Assignee: Matt Sicker
>
> As I wonder how to prefix yet another configurable system property, I noticed 
> we have five families of configuration name prefixes:
> log4j.*
> log4j2.*
> Log4j*
> org.apache.logging.log4j.*
> 
> What I'd like to do is strip out all those prefixes and allow any of them, 
> but change the documentation to use only a single consistent prefix. This 
> would also make it simpler when writing the properties into a 
> log4j2.component.properties file as you could omit all the prefixes as they 
> won't clash with other libraries.



--
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



[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

2017-02-05 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853311#comment-15853311
 ] 

ASF subversion and git services commented on LOG4J2-1431:
-

Commit a9bcf176cc154fadae2a464c9743788809cf8ae6 in logging-log4j2's branch 
refs/heads/LOG4J2-1431 from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=a9bcf17 ]

[LOG4J2-1809]: Add global configuration environment SPI

This adds a PropertySource service provider interface for providing
global configuration properties. This also refactors support in
LOG4J2-1431 to use these PropertySource providers.


> Simplify log4j system property naming scheme
> 
>
> Key: LOG4J2-1431
> URL: https://issues.apache.org/jira/browse/LOG4J2-1431
> Project: Log4j 2
>  Issue Type: Improvement
>Reporter: Matt Sicker
>Assignee: Matt Sicker
>
> As I wonder how to prefix yet another configurable system property, I noticed 
> we have five families of configuration name prefixes:
> log4j.*
> log4j2.*
> Log4j*
> org.apache.logging.log4j.*
> 
> What I'd like to do is strip out all those prefixes and allow any of them, 
> but change the documentation to use only a single consistent prefix. This 
> would also make it simpler when writing the properties into a 
> log4j2.component.properties file as you could omit all the prefixes as they 
> won't clash with other libraries.



--
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



[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

2017-02-04 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852706#comment-15852706
 ] 

ASF subversion and git services commented on LOG4J2-1431:
-

Commit bd587cf4e514a62ecd3852e6f1182feeed049fdc in logging-log4j2's branch 
refs/heads/LOG4J2-1431 from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=bd587cf ]

[LOG4J2-1431]: Provide support for simplified global configuration environment

This provides the base support for implementing simplified property names along 
with environment variable support.


> Simplify log4j system property naming scheme
> 
>
> Key: LOG4J2-1431
> URL: https://issues.apache.org/jira/browse/LOG4J2-1431
> Project: Log4j 2
>  Issue Type: Improvement
>Reporter: Matt Sicker
>
> As I wonder how to prefix yet another configurable system property, I noticed 
> we have five families of configuration name prefixes:
> log4j.*
> log4j2.*
> Log4j*
> org.apache.logging.log4j.*
> 
> What I'd like to do is strip out all those prefixes and allow any of them, 
> but change the documentation to use only a single consistent prefix. This 
> would also make it simpler when writing the properties into a 
> log4j2.component.properties file as you could omit all the prefixes as they 
> won't clash with other libraries.



--
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



[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

2016-06-15 Thread Matt Sicker (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333099#comment-15333099
 ] 

Matt Sicker commented on LOG4J2-1431:
-

Won't need it any more if I refactor the BlockingQueueFactory into a plugin.

> Simplify log4j system property naming scheme
> 
>
> Key: LOG4J2-1431
> URL: https://issues.apache.org/jira/browse/LOG4J2-1431
> Project: Log4j 2
>  Issue Type: Improvement
>Reporter: Matt Sicker
>
> As I wonder how to prefix yet another configurable system property, I noticed 
> we have five families of configuration name prefixes:
> log4j.*
> log4j2.*
> Log4j*
> org.apache.logging.log4j.*
> 
> What I'd like to do is strip out all those prefixes and allow any of them, 
> but change the documentation to use only a single consistent prefix. This 
> would also make it simpler when writing the properties into a 
> log4j2.component.properties file as you could omit all the prefixes as they 
> won't clash with other libraries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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



[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

2016-06-15 Thread Ralph Goers (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333074#comment-15333074
 ] 

Ralph Goers commented on LOG4J2-1431:
-

I agree. But what system property are you planning on adding Matt?

> Simplify log4j system property naming scheme
> 
>
> Key: LOG4J2-1431
> URL: https://issues.apache.org/jira/browse/LOG4J2-1431
> Project: Log4j 2
>  Issue Type: Improvement
>Reporter: Matt Sicker
>
> As I wonder how to prefix yet another configurable system property, I noticed 
> we have five families of configuration name prefixes:
> log4j.*
> log4j2.*
> Log4j*
> org.apache.logging.log4j.*
> 
> What I'd like to do is strip out all those prefixes and allow any of them, 
> but change the documentation to use only a single consistent prefix. This 
> would also make it simpler when writing the properties into a 
> log4j2.component.properties file as you could omit all the prefixes as they 
> won't clash with other libraries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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



[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

2016-06-15 Thread Remko Popma (JIRA)

[ 
https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333049#comment-15333049
 ] 

Remko Popma commented on LOG4J2-1431:
-

I like this idea. 
For the docs, I would also prefer {{log4j2}}.

> Simplify log4j system property naming scheme
> 
>
> Key: LOG4J2-1431
> URL: https://issues.apache.org/jira/browse/LOG4J2-1431
> Project: Log4j 2
>  Issue Type: Improvement
>Reporter: Matt Sicker
>
> As I wonder how to prefix yet another configurable system property, I noticed 
> we have five families of configuration name prefixes:
> log4j.*
> log4j2.*
> Log4j*
> org.apache.logging.log4j.*
> 
> What I'd like to do is strip out all those prefixes and allow any of them, 
> but change the documentation to use only a single consistent prefix. This 
> would also make it simpler when writing the properties into a 
> log4j2.component.properties file as you could omit all the prefixes as they 
> won't clash with other libraries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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