[jira] [Created] (LOG4J2-1498) [Java 9] fix dependency on old JDK versioning scheme

2016-08-03 Thread Remko Popma (JIRA)
Remko Popma created LOG4J2-1498: --- Summary: [Java 9] fix dependency on old JDK versioning scheme Key: LOG4J2-1498 URL: https://issues.apache.org/jira/browse/LOG4J2-1498 Project: Log4j 2 Issue

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

2016-08-03 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-1496) Update Kafka client from 0.9.1.0 to 0.10.0.0

2016-08-03 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1496. Resolution: Fixed In Git master. > Update Kafka client from 0.9.1.0 to 0.10.0.0 >

Re: logging-log4j2 git commit: Use the standard US English spelling for "behavior".

2016-08-03 Thread Gary Gregory
For me, It's just unpolished to have a mix of styles. As I was raised in France, should I start peppering code and docs with French expressions? /* Zut alors! */ I prefer consistency, it could be British English, US English, Proto-Bantu, whatever. I just it's lame and not very pro to have a mix

Re: logging-log4j2 git commit: [LOG4J2-1482] Improper header in CsvParameterLayout.

2016-08-03 Thread Gary Gregory
I implemented the fix this way because it seems wrong to have the default log event factory coded in the AbstactStringLayout. Right now this use case is only for headers and footers. So the changes make that explicit by accessing the default log event factory from the header and footer methods.

[jira] [Created] (LOG4J2-1497) Update JMS test from ActiveMQ 5.13.3 to 5.13.4

2016-08-03 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-1497: Summary: Update JMS test from ActiveMQ 5.13.3 to 5.13.4 Key: LOG4J2-1497 URL: https://issues.apache.org/jira/browse/LOG4J2-1497 Project: Log4j 2 Issue Type:

[jira] [Created] (LOG4J2-1496) Update Kafka client from 0.9.1.0 to 0.10.0.0

2016-08-03 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-1496: Summary: Update Kafka client from 0.9.1.0 to 0.10.0.0 Key: LOG4J2-1496 URL: https://issues.apache.org/jira/browse/LOG4J2-1496 Project: Log4j 2 Issue Type:

[jira] [Closed] (LOG4J2-1495) Update LMAX Disruptor from 3.3.4 to 3.3.5.

2016-08-03 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1495. Resolution: Fixed It Git master. > Update LMAX Disruptor from 3.3.4 to 3.3.5. >

[jira] [Commented] (LOG4J2-1235) org.apache.logging.log4j.core.appender.routing.IdlePurgePolicy not working correctly

2016-08-03 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406864#comment-15406864 ] ASF GitHub Bot commented on LOG4J2-1235: Github user remkop commented on the issue:

Jenkins build became unstable: Log4j 2.x #2120

2016-08-03 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

Re: logging-log4j2 git commit: Use the standard US English spelling for "behavior".

2016-08-03 Thread Matt Sicker
I like British English myself. On 3 August 2016 at 18:23, Remko Popma wrote: > We never agreed that there is any need to standardize on a particular > flavour of the English language. Let's celebrate our diversity and the fact > that we are a global community. I

Re: logging-log4j2 git commit: Use the standard US English spelling for "behavior".

2016-08-03 Thread Remko Popma
We never agreed that there is any need to standardize on a particular flavour of the English language. Let's celebrate our diversity and the fact that we are a global community. I respectfully ask that this change is reverted. -Remko On Thursday, 4 August 2016, wrote: >

Re: logging-log4j2 git commit: [LOG4J2-1482] Improper header in CsvParameterLayout.

2016-08-03 Thread Remko Popma
(Sorry, accidentally hit Send on phone) Why is this fixed in AbstactStringLayout, with ripple effect to JSON and YAML layouts? The problem seems to be in Serializer. It is still unclear to me why Serializer needs a LogEvent, (away from PC now) but I assume it is because of StrSubstitutor. I

Re: logging-log4j2 git commit: [LOG4J2-1482] Improper header in CsvParameterLayout.

2016-08-03 Thread Remko Popma
Why is this fixed in AbstactStringLayout, with ripple effect to JSON and YAML layouts? The problem seems to be in Serializer. It is still unclear to me why Serializer needs a LogEvent, (away from PC now) but I assume it is because of StrSubstitutor. I would like it much better if

[jira] [Closed] (LOG4J2-1494) Update Jackson from 2.8.0 to 2.8.1

2016-08-03 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1494. Resolution: Fixed In Git master. > Update Jackson from 2.8.0 to 2.8.1 >

[jira] [Created] (LOG4J2-1495) Update LMAX Disruptor from 3.3.4 to 3.3.5.

2016-08-03 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-1495: Summary: Update LMAX Disruptor from 3.3.4 to 3.3.5. Key: LOG4J2-1495 URL: https://issues.apache.org/jira/browse/LOG4J2-1495 Project: Log4j 2 Issue Type:

[jira] [Created] (LOG4J2-1494) Update Jackson from 2.8.0 to 2.8.1

2016-08-03 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-1494: Summary: Update Jackson from 2.8.0 to 2.8.1 Key: LOG4J2-1494 URL: https://issues.apache.org/jira/browse/LOG4J2-1494 Project: Log4j 2 Issue Type: Improvement

[jira] [Updated] (LOG4J2-1493) Cannot set all appenders as async when including kafkaappender

2016-08-03 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1493: - Description: When I set this property: {noformat}

[jira] [Resolved] (LOG4J2-1482) Improper header in CsvParameterLayout

2016-08-03 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1482. -- Resolution: Fixed Fix Version/s: 2.7 Please verify and close. > Improper header in

[jira] [Commented] (LOG4J2-1482) Improper header in CsvParameterLayout

2016-08-03 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406697#comment-15406697 ] Remko Popma commented on LOG4J2-1482: - Gary, rollover is not garbagefree (and I have no plans to

[jira] [Commented] (LOG4J2-1235) org.apache.logging.log4j.core.appender.routing.IdlePurgePolicy not working correctly

2016-08-03 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406590#comment-15406590 ] ASF GitHub Bot commented on LOG4J2-1235: Github user frendos commented on the issue:

[jira] [Created] (LOG4J2-1493) Cannot set all appenders as async when including kafkaappender

2016-08-03 Thread Jose Leon (JIRA)
Jose Leon created LOG4J2-1493: - Summary: Cannot set all appenders as async when including kafkaappender Key: LOG4J2-1493 URL: https://issues.apache.org/jira/browse/LOG4J2-1493 Project: Log4j 2

[jira] [Commented] (LOG4J2-1482) Improper header in CsvParameterLayout

2016-08-03 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406562#comment-15406562 ] Gary Gregory commented on LOG4J2-1482: -- The problem is in the method

Re: Log4j Scala API

2016-08-03 Thread Mikael Ståldal
Sure, it is not a big hurry. On Wed, Aug 3, 2016 at 3:55 PM, Ralph Goers wrote: > I have been swamped at work. It will take me a couple of days to look at > this. > > Ralph > > On Aug 3, 2016, at 4:43 AM, Mikael Ståldal > wrote: > > I

Re: Log4j Scala API

2016-08-03 Thread Ralph Goers
I have been swamped at work. It will take me a couple of days to look at this. Ralph > On Aug 3, 2016, at 4:43 AM, Mikael Ståldal wrote: > > I think that the Scala API I have been working on for quite long is ready now. > > Any objections to merging the branch

[jira] [Commented] (LOG4J2-1480) CronTriggeringPolicy timing / file deletion issue

2016-08-03 Thread Stefano Ongeri (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405822#comment-15405822 ] Stefano Ongeri commented on LOG4J2-1480: I'm experiencing the same issue in one of my projects.

Log4j Scala API

2016-08-03 Thread Mikael Ståldal
I think that the Scala API I have been working on for quite long is ready now. Any objections to merging the branch LOG4J-1181 to master? https://issues.apache.org/jira/browse/LOG4J2-1181 -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* mikael.stal...@magine.com

[jira] [Created] (LOG4J2-1492) Log4j2 implementation of jetty's RequestLog

2016-08-03 Thread Mohan Kumar Pandian (JIRA)
Mohan Kumar Pandian created LOG4J2-1492: --- Summary: Log4j2 implementation of jetty's RequestLog Key: LOG4J2-1492 URL: https://issues.apache.org/jira/browse/LOG4J2-1492 Project: Log4j 2