Re: Import Ordering - ImpSort

My bad, here is a link sir. http://code.revelc.net/impsort-maven-plugin/ On Fri, Oct 13, 2017 at 7:35 PM, Matt Sicker wrote: > What's the plugin? I like the idea in theory at least. I've been dragged > into import-related formatting wars in past jobs, and having a consistent

Re: [1/4] logging-log4j2 git commit: LOG4J2-2062 Added property to KafkaAppender to send a Key to Kafka

If you use @PluginBuilderAttribute, you can omit the names if they match the field name. Also, default values can be specified in normal Java code as the default field values. Less verbose IMO. On 13 October 2017 at 14:38, wrote: > Repository: logging-log4j2 > Updated

Re: Import Ordering - ImpSort

What's the plugin? I like the idea in theory at least. I've been dragged into import-related formatting wars in past jobs, and having a consistent way to handle them would be great (although I think you can configure checkstyle to enforce it, checkstyle doesn't actually format anything for you).

Build failed in Jenkins: Log4j 2.x #3119

See Changes: [mikael] LOG4J2-2062 Added property to KafkaAppender to send a Key to Kafka [mikael] LOG4J2-2062 Fix documentation [mikael] LOG4J2-2062 Fix formatting --

[jira] [Commented] (LOG4J2-2074) The console appender should say why it cannot load JAnsi

[ https://issues.apache.org/jira/browse/LOG4J2-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204197#comment-16204197 ] ASF subversion and git services commented on LOG4J2-2074: - Commit

[jira] [Closed] (LOG4J2-2074) The console appender should say why it cannot load JAnsi

[ https://issues.apache.org/jira/browse/LOG4J2-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2074. Resolution: Fixed Fix Version/s: 2.10.0 In git master. > The console appender should say

[jira] [Created] (LOG4J2-2074) The console appender should say why it cannot load JAnsi

Gary Gregory created LOG4J2-2074: Summary: The console appender should say why it cannot load JAnsi Key: LOG4J2-2074 URL: https://issues.apache.org/jira/browse/LOG4J2-2074 Project: Log4j 2

[jira] [Closed] (LOG4J2-2073) Log4j-config.xsd should make AppenderRef optional for each Logger element

[ https://issues.apache.org/jira/browse/LOG4J2-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-2073. Resolution: Fixed Fix Version/s: 2.10.0 In git master. > Log4j-config.xsd should make

[jira] [Commented] (LOG4J2-2073) Log4j-config.xsd should make AppenderRef optional for each Logger element

[ https://issues.apache.org/jira/browse/LOG4J2-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204187#comment-16204187 ] ASF subversion and git services commented on LOG4J2-2073: - Commit

Re: Logging list for emails generated by tools

Sounds like a good idea. On 2017-10-12 22:34, Ralph Goers wrote: What do others think about the idea of creating a separate mailing list for emails generated by tools? This list gets a bit noisy from all the extra emails and I have a hard time filtering this list because of how some of the

[jira] [Commented] (LOG4J2-2062) Add possibility of sending the key of a message to Kafka using KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204073#comment-16204073 ] Mikael Ståldal commented on LOG4J2-2062: The first PR is now merged. > Add possibility of

[jira] [Commented] (LOG4J2-2062) Add possibility of sending the key of a message to Kafka using KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204070#comment-16204070 ] ASF subversion and git services commented on LOG4J2-2062: - Commit

[GitHub] logging-log4j2 pull request #112: LOG4J2-2062 Added property to KafkaAppende...

Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j2/pull/112 ---

[jira] [Commented] (LOG4J2-2062) Add possibility of sending the key of a message to Kafka using KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204062#comment-16204062 ] ASF GitHub Bot commented on LOG4J2-2062: Github user mikaelstaldal commented on the issue:

[GitHub] logging-log4j2 issue #112: LOG4J2-2062 Added property to KafkaAppender to se...

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/112 :+1: ---

Re: Logging list for emails generated by tools

We haven't really discussed the use of gitbox in this project yet, so that's not an issue right now. What we do have is a sync between PR comments to the mentioned JIRA ticket, and that generates duplicate emails as it is. On 13 October 2017 at 01:56, Daan Hoogland

Re: appender Failover has no parameter that matches element Failovers

Can you post your log4j2 configuration? I’ve seen some issues while using failover appender. On 13 Oct 2017, 6:00 PM +0530, gaurav9...@gmail.com , wrote: > Hi log4j2 developers, > > I am getting following error while configuring 'failoverappender' for my > primary

appender Failover has no parameter that matches element Failovers

Hi log4j2 developers, I am getting following error while configuring 'failoverappender' for my primary 'console appender': appender Failover has no parameter that matches element Failovers P.S. I have set ignoreExceptions="false" for the primary 'console appender' Log4j2 version: 2.9.0

Re: Logging list for emails generated by tools

I don’t know if logging is a gitbox project but keep in mind that also a lot of the github discussions will disappear if you do this. On 13/10/2017, 00:56, "Remko Popma" wrote: I think that's a good idea. (I really wish we could have fewer duplicate emails though.)