Re: Duplication?

2016-12-13 Thread Matt Sicker 
I've considered that long ago, but despite having the same structure, they
seem to have different use cases.

On 13 December 2016 at 20:49, Gary Gregory  wrote:

> We have:
>
> - org.apache.logging.log4j.core.config.Property
> - org.apache.logging.log4j.core.util.KeyValuePair
>
> which seem to server the same purpose.
>
> Should we deprecate one in favor of the other?
>
> Gary
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
>
> 
> JUnit in Action, Second Edition
> 
>
> 
> Spring Batch in Action
> 
> 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Matt Sicker

Duplication?

2016-12-13 Thread Gary Gregory 
We have:

- org.apache.logging.log4j.core.config.Property
- org.apache.logging.log4j.core.util.KeyValuePair

which seem to server the same purpose.

Should we deprecate one in favor of the other?

Gary

-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition



JUnit in Action, Second Edition



Spring Batch in Action


Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Jenkins build became unstable: Log4j 2.x #2534

2016-12-13 Thread Apache Jenkins Server 
See 


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

Jenkins build is back to stable : Log4j 2.x #2532

2016-12-13 Thread Apache Jenkins Server 
See 


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

[jira] [Closed] (LOG4J2-1738) Add a Builder to JsonLayout and deprecate org.apache.logging.log4j.core.layout.JsonLayout.createLayout(Configuration, boolean, boolean, boolean, boolean, boolean, boolean

2016-12-13 Thread Gary Gregory (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary Gregory closed LOG4J2-1738.

   Resolution: Fixed
Fix Version/s: 2.8

Closing. In Git master.

> Add a Builder to JsonLayout and deprecate 
> org.apache.logging.log4j.core.layout.JsonLayout.createLayout(Configuration, 
> boolean, boolean, boolean, boolean, boolean, boolean, String, String, 
> Charset, boolean)
> -
>
> Key: LOG4J2-1738
> URL: https://issues.apache.org/jira/browse/LOG4J2-1738
> Project: Log4j 2
>  Issue Type: New Feature
>  Components: Layouts
>Affects Versions: 2.7
>Reporter: Gary Gregory
>Assignee: Gary Gregory
> Fix For: 2.8
>
>
> Add a Builder to {{JsonLayout}} and deprecate 
> {{JsonLayout.createLayout(Configuration, boolean, boolean, boolean, boolean, 
> boolean, boolean, String, String, Charset, boolean)}}



--
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] [Comment Edited] (LOG4J2-1302) log4j-slf4j-impl should provide a runtime dependency on log4j-core

2016-12-13 Thread Neon (JIRA) 

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

Neon edited comment on LOG4J2-1302 at 12/13/16 9:41 PM:


well, the current documentation is misleading. it should say that it is a 
log4j-api-slf4j-impl 
and it should probably have *note* to add log4j-core as runtime dependency. e.g.

The Log4j 2 SLF4J Binding description should be updated at 
https://logging.apache.org/log4j/2.0/log4j-slf4j-impl/index.html
From:
The Log4j 2 SLF4J Binding allows applications coded to the SLF4J API to use 
Log4j 2 as the implementation.
To:
The Log4j 2 SLF4J Binding allows applications coded to the SLF4J API to use 
Log4j 2 API as the implementation.
and maybe under Usage section: put a note, that most user's will probably add 
*log4j-core* as a *runtime* dependency.



was (Author: neon):
well, the current documentation is misleading. it should say that it is a 
log4j-api-slf4j-impl 
and it should probably have not to add log4j-core as runtime dependency. e.g.

The Log4j 2 SLF4J Binding description should be updated at 
https://logging.apache.org/log4j/2.0/log4j-slf4j-impl/index.html
From:
The Log4j 2 SLF4J Binding allows applications coded to the SLF4J API to use 
Log4j 2 as the implementation.
To:
The Log4j 2 SLF4J Binding allows applications coded to the SLF4J API to use 
Log4j 2 API as the implementation.
and maybe under Usage section: put a note, that most user's will probably add 
*log4j-core* as a *runtime* dependency.


> log4j-slf4j-impl should provide a runtime dependency on log4j-core
> --
>
> Key: LOG4J2-1302
> URL: https://issues.apache.org/jira/browse/LOG4J2-1302
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: SLF4J Bridge
>Reporter: Steve Davids
>
> After pulling in the log4j-slf4j-impl I was surprised to find out that I also 
> needed to add the the log4j-core dependency myself instead of the dependency 
> pulled in automatically from the log4j-slf4j-impl pom. I was expecting the 
> behavior provided by slf4j-log4j12 which does pull in the appropriate 
> implementation to get going immediately.



--
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-1302) log4j-slf4j-impl should provide a runtime dependency on log4j-core

2016-12-13 Thread Neon (JIRA) 

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

Neon commented on LOG4J2-1302:
--

well, the current documentation is misleading. it should say that it is a 
log4j-api-slf4j-impl 
and it should probably have not to add log4j-core as runtime dependency. e.g.

The Log4j 2 SLF4J Binding description should be updated at 
https://logging.apache.org/log4j/2.0/log4j-slf4j-impl/index.html
From:
The Log4j 2 SLF4J Binding allows applications coded to the SLF4J API to use 
Log4j 2 as the implementation.
To:
The Log4j 2 SLF4J Binding allows applications coded to the SLF4J API to use 
Log4j 2 API as the implementation.
and maybe under Usage section: put a note, that most user's will probably add 
*log4j-core* as a *runtime* dependency.


> log4j-slf4j-impl should provide a runtime dependency on log4j-core
> --
>
> Key: LOG4J2-1302
> URL: https://issues.apache.org/jira/browse/LOG4J2-1302
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: SLF4J Bridge
>Reporter: Steve Davids
>
> After pulling in the log4j-slf4j-impl I was surprised to find out that I also 
> needed to add the the log4j-core dependency myself instead of the dependency 
> pulled in automatically from the log4j-slf4j-impl pom. I was expecting the 
> behavior provided by slf4j-log4j12 which does pull in the appropriate 
> implementation to get going immediately.



--
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-1302) log4j-slf4j-impl should provide a runtime dependency on log4j-core

2016-12-13 Thread Ralph Goers (JIRA) 

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

Ralph Goers commented on LOG4J2-1302:
-

We seem to get a lot of those.

> log4j-slf4j-impl should provide a runtime dependency on log4j-core
> --
>
> Key: LOG4J2-1302
> URL: https://issues.apache.org/jira/browse/LOG4J2-1302
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: SLF4J Bridge
>Reporter: Steve Davids
>
> After pulling in the log4j-slf4j-impl I was surprised to find out that I also 
> needed to add the the log4j-core dependency myself instead of the dependency 
> pulled in automatically from the log4j-slf4j-impl pom. I was expecting the 
> behavior provided by slf4j-log4j12 which does pull in the appropriate 
> implementation to get going immediately.



--
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] [Created] (LOG4J2-1738) Add a Builder to JsonLayout and deprecate org.apache.logging.log4j.core.layout.JsonLayout.createLayout(Configuration, boolean, boolean, boolean, boolean, boolean, boolea

2016-12-13 Thread Gary Gregory (JIRA) 
Gary Gregory created LOG4J2-1738:


 Summary: Add a Builder to JsonLayout and deprecate 
org.apache.logging.log4j.core.layout.JsonLayout.createLayout(Configuration, 
boolean, boolean, boolean, boolean, boolean, boolean, String, String, Charset, 
boolean)
 Key: LOG4J2-1738
 URL: https://issues.apache.org/jira/browse/LOG4J2-1738
 Project: Log4j 2
  Issue Type: New Feature
  Components: Layouts
Affects Versions: 2.7
Reporter: Gary Gregory
Assignee: Gary Gregory


Add a Builder to {{JsonLayout}} and deprecate 
{{JsonLayout.createLayout(Configuration, boolean, boolean, boolean, boolean, 
boolean, boolean, String, String, Charset, boolean)}}



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

Jenkins build is still unstable: Log4j 2.x #2531

2016-12-13 Thread Apache Jenkins Server 
See 


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

[jira] [Commented] (LOG4J2-1620) 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not false

2016-12-13 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on LOG4J2-1620:


GitHub user thedutchy opened a pull request:

https://github.com/apache/logging-log4j2/pull/50

[LOG4J2-1620] Add sync.send configuration property to Kafka Appender …

…to support asynchronous sends

This change is backwards compatible, as the property is set to "true" by 
default. The implementation mirrors the implementation of the 
KafkaLog4jAppender in the Apache Kafka project (which is however based on log4j 
instead of log4j2).

The asynchronous send is relevant, as it significantly improves throughput 
to the Kafka broker. On my machine, setting the property to false, lead to a 
throughput improvement of approximately 50x.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/thedutchy/logging-log4j2 LOG4J2-1620

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/logging-log4j2/pull/50.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #50


commit e07d9861c081c331cebbfc5bbc946b81afeeedbf
Author: Vincent Tieleman 
Date:   2016-12-13T19:42:41Z

[LOG4J2-1620] Add sync.send configuration property to Kafka Appender to 
support asynchronous sends




> 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not 
> false
> ---
>
> Key: LOG4J2-1620
> URL: https://issues.apache.org/jira/browse/LOG4J2-1620
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Appenders
>Affects Versions: 2.7
>Reporter: Sascha Scholz
>Assignee: Gary Gregory
>
> The default value of the immediaFlush property in RollingFile appender was 
> changed from true to false (compared with 2.6.2). The change was introduced 
> with
> {noformat}
> a82794f06e3bc095ef0bca41b98c5d1ea915de76 is the first bad commit
> commit a82794f06e3bc095ef0bca41b98c5d1ea915de76
> Author: Gary Gregory 
> Date:   Fri Aug 19 17:27:26 2016 -0700
> [LOG4J2-1504] RollingFileAppender should be able to create files
> on-demand.
> :04 04 3d3faa81429c2ff83db3b1672a2700e2efe770e3 
> 279da0b08553454f69fdbebfcdb855b21dc7c2ae Mlog4j-core
> :04 04 9548cb83e88b752d42e80ef6cab3463eed9b868c 
> 5a23c7038b1f4bb49c8b6b8727d4a681db3c2ae8 Msrc
> {noformat}
> It looks to me from the commit message that this change was not intended. And 
> it breaks my current usage. I'd have to explicitly set the value to true now 
> in order to avoid a regression in my code.



--
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-1473) Inform other Apache projects using Log4j 1.x that it won't be supported in JDK9

2016-12-13 Thread Greg Thomas (JIRA) 

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

Greg Thomas commented on LOG4J2-1473:
-

At first glance, it should just be a straight swap-out, I don't think anything 
particularly tricky is going on with the logging - at least in the cursory 
glance of the client API that I looked at. But that's just an outsiders view 
looking on in.

> Inform other Apache projects using Log4j 1.x that it won't be supported in 
> JDK9
> ---
>
> Key: LOG4J2-1473
> URL: https://issues.apache.org/jira/browse/LOG4J2-1473
> Project: Log4j 2
>  Issue Type: Umbrella
>Reporter: Matt Sicker
>
> Due to various issues in Log4j 1.2.x, it will no longer work in JDK9: 
> http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008654.html
> As Log4j 1.x is EOL, we are not adding new updates, so Apache projects that 
> are using Log4j 1.x still should be informed of the pending issues. We can 
> offer help to upgrade to Log4j 2.x.
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> This issue is a collector for the various projects that are still using Log4j 
> 1.x. Each project should be made into a subtask of this issue.



--
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-1473) Inform other Apache projects using Log4j 1.x that it won't be supported in JDK9

2016-12-13 Thread Remko Popma (JIRA) 

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

Remko Popma commented on LOG4J2-1473:
-

In general I applaud any effort to move away from slf4j towards using the 
Log4j2 API. 

I'm not sure what work is outstanding for Apache Directory?

> Inform other Apache projects using Log4j 1.x that it won't be supported in 
> JDK9
> ---
>
> Key: LOG4J2-1473
> URL: https://issues.apache.org/jira/browse/LOG4J2-1473
> Project: Log4j 2
>  Issue Type: Umbrella
>Reporter: Matt Sicker
>
> Due to various issues in Log4j 1.2.x, it will no longer work in JDK9: 
> http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008654.html
> As Log4j 1.x is EOL, we are not adding new updates, so Apache projects that 
> are using Log4j 1.x still should be informed of the pending issues. We can 
> offer help to upgrade to Log4j 2.x.
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> This issue is a collector for the various projects that are still using Log4j 
> 1.x. Each project should be made into a subtask of this issue.



--
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] [Comment Edited] (LOG4J2-1733) Introduce SyncSend property for KafkaAppender (as in KafkaLog4jAppender)

2016-12-13 Thread JIRA 

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

Mikael Ståldal edited comment on LOG4J2-1733 at 12/13/16 11:35 AM:
---

Yes, we can add such option to KafkaAppender. It should not be enabled by 
default though. Can you provide a patch?


was (Author: mikaelstaldal):
Yes, we can add such option to KafkaAppender. It should not be enabled by 
default though.

> Introduce SyncSend property for KafkaAppender (as in KafkaLog4jAppender)
> 
>
> Key: LOG4J2-1733
> URL: https://issues.apache.org/jira/browse/LOG4J2-1733
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Appenders
>Affects Versions: 2.5
> Environment: Kafka 0.10.1.0
>Reporter: Vincent Tieleman
>Assignee: Mikael Ståldal
>
> The KafkaLog4jAppender (shipped with Kafka and usable with log4j), has a 
> syncsend property that improves performance significantly by not blocking a 
> send to Kafka. I've tried many other configuration settings and setups, but 
> find that none of these approaches improved the logging performance to Kafka 
> as significantly as setting the syncsend property to false.
> Unfortunately, the syncsend property is not supported by the KafkaAppender 
> shipped with log4j2 and the KafkaLog4jAppender only supports log4j, so I am 
> stuck with forking the code and making the change myself.
> Could you please introduce this property in the KafkaAppender in log4j2?



--
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-1733) Introduce SyncSend property for KafkaAppender (as in KafkaLog4jAppender)

2016-12-13 Thread JIRA 

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

Mikael Ståldal commented on LOG4J2-1733:


Yes, we can add such option to KafkaAppender. It should not be enabled by 
default though.

> Introduce SyncSend property for KafkaAppender (as in KafkaLog4jAppender)
> 
>
> Key: LOG4J2-1733
> URL: https://issues.apache.org/jira/browse/LOG4J2-1733
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Appenders
>Affects Versions: 2.5
> Environment: Kafka 0.10.1.0
>Reporter: Vincent Tieleman
>Assignee: Mikael Ståldal
>
> The KafkaLog4jAppender (shipped with Kafka and usable with log4j), has a 
> syncsend property that improves performance significantly by not blocking a 
> send to Kafka. I've tried many other configuration settings and setups, but 
> find that none of these approaches improved the logging performance to Kafka 
> as significantly as setting the syncsend property to false.
> Unfortunately, the syncsend property is not supported by the KafkaAppender 
> shipped with log4j2 and the KafkaLog4jAppender only supports log4j, so I am 
> stuck with forking the code and making the change myself.
> Could you please introduce this property in the KafkaAppender in log4j2?



--
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] [Assigned] (LOG4J2-1733) Introduce SyncSend property for KafkaAppender (as in KafkaLog4jAppender)

2016-12-13 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal reassigned LOG4J2-1733:
--

Assignee: Mikael Ståldal

> Introduce SyncSend property for KafkaAppender (as in KafkaLog4jAppender)
> 
>
> Key: LOG4J2-1733
> URL: https://issues.apache.org/jira/browse/LOG4J2-1733
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Appenders
>Affects Versions: 2.5
> Environment: Kafka 0.10.1.0
>Reporter: Vincent Tieleman
>Assignee: Mikael Ståldal
>
> The KafkaLog4jAppender (shipped with Kafka and usable with log4j), has a 
> syncsend property that improves performance significantly by not blocking a 
> send to Kafka. I've tried many other configuration settings and setups, but 
> find that none of these approaches improved the logging performance to Kafka 
> as significantly as setting the syncsend property to false.
> Unfortunately, the syncsend property is not supported by the KafkaAppender 
> shipped with log4j2 and the KafkaLog4jAppender only supports log4j, so I am 
> stuck with forking the code and making the change myself.
> Could you please introduce this property in the KafkaAppender in log4j2?



--
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-1473) Inform other Apache projects using Log4j 1.x that it won't be supported in JDK9

2016-12-13 Thread Greg Thomas (JIRA) 

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

Greg Thomas commented on LOG4J2-1473:
-

I've just started using the Apache LDAP client API, part of the Apache 
Directory project - http://directory.apache.org/

The client API (and presumably other components of Apache Directory) are using 
SLF4J.

It's not strictly an upgrade from Log4j1 so perhaps not part of this parent 
JIRA, but I'd like to think it would be an upgrade to move to Log4j2. Should 
Apache Directory be added as a sub-task ?

> Inform other Apache projects using Log4j 1.x that it won't be supported in 
> JDK9
> ---
>
> Key: LOG4J2-1473
> URL: https://issues.apache.org/jira/browse/LOG4J2-1473
> Project: Log4j 2
>  Issue Type: Umbrella
>Reporter: Matt Sicker
>
> Due to various issues in Log4j 1.2.x, it will no longer work in JDK9: 
> http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008654.html
> As Log4j 1.x is EOL, we are not adding new updates, so Apache projects that 
> are using Log4j 1.x still should be informed of the pending issues. We can 
> offer help to upgrade to Log4j 2.x.
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> This issue is a collector for the various projects that are still using Log4j 
> 1.x. Each project should be made into a subtask of this issue.



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