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.) Remko

Re: Build failed in Jenkins: Log4j 2.x #3117

Sigh, but how? G On Thu, Oct 12, 2017 at 5:11 PM, Ralph Goers wrote: > One of the Jenkins servers must be misconfigured. > > Ralph > > > On Oct 12, 2017, at 3:37 PM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > > > > See

Re: [Log4j] skipJansi by default

We don't have much choice I think. As Ralph pointed out, we have to change the default value as it can cause application startup to fail... > On Oct 13, 2017, at 4:25, Gary Gregory wrote: > > My preference is to leave it as. The 2nd option is to add jansi=true|false > to the ConsoleAppender

Build failed in Jenkins: Log4j 2.x #3118

See Changes: [ggregory] The next version will be 2.10.0. -- [...truncated 4.72 MB...] [JENKINS] Archiving

[jira] [Commented] (LOG4J2-1982) Log4j-config.xsd only allows one AppenderRef element for each Logger element

[ https://issues.apache.org/jira/browse/LOG4J2-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202777#comment-16202777 ] Gary Gregory commented on LOG4J2-1982: -- Right! Fixing with https://issues.apache.org

Re: Build failed in Jenkins: Log4j 2.x #3117

One of the Jenkins servers must be misconfigured. Ralph > On Oct 12, 2017, at 3:37 PM, Apache Jenkins Server > wrote: > > See > > > Changes: > > [ggregory] [LOG4J2-1216] Nested pattern layout options broken. App

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

Gary Gregory created LOG4J2-2073: Summary: Log4j-config.xsd should make AppenderRef optional for each Logger element Key: LOG4J2-2073 URL: https://issues.apache.org/jira/browse/LOG4J2-2073 Project: Lo

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202771#comment-16202771 ] Ralph Goers edited comment on LOG4J2-2056 at 10/12/17 11:07 PM: ---

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202771#comment-16202771 ] Ralph Goers commented on LOG4J2-2056: - What you described is pretty much how Log4j al

Re: Logging list for emails generated by tools

I think that's a good idea. (I really wish we could have fewer duplicate emails though.) Remko > On Oct 13, 2017, at 6:59, Dominik Psenner wrote: > > Stuff that requires human intervention should stay prominent. The rest can > go away. :-) > > 2017-10-12 23:06 GMT+02:00 Ralph Goers : > >> I

Build failed in Jenkins: Log4j 2.x #3117

See Changes: [ggregory] [LOG4J2-1216] Nested pattern layout options broken. Apply slightly -- [...truncated 4.77 MB...] Downloading: https://repository.apache.org/content/repo

Re: Logging list for emails generated by tools

Stuff that requires human intervention should stay prominent. The rest can go away. :-) 2017-10-12 23:06 GMT+02:00 Ralph Goers : > It will also make the quarterly board reports more accurate. > reporter.apache.org provides the number of emails received on the list > during the quarter. In my view

Jenkins build is back to normal : Log4j 2.x #3116

See

[jira] [Resolved] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1216. -- Resolution: Fixed PR 116 applied. Please verify and close. Note that the unit test {{org.apach

[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202676#comment-16202676 ] ASF GitHub Bot commented on LOG4J2-1216: Github user asfgit closed the pull reque

[GitHub] logging-log4j2 pull request #116: [LOG4J2-1216] fix PatternParser for patter...

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

[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

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

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202658#comment-16202658 ] Neil Bartlett commented on LOG4J2-2056: --- Whatever name you choose, that is the name

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202635#comment-16202635 ] Ralph Goers edited comment on LOG4J2-2056 at 10/12/17 9:19 PM:

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202635#comment-16202635 ] Ralph Goers commented on LOG4J2-2056: - [~njbartlett] Thanks for jumping in. The optio

Re: Logging list for emails generated by tools

It will also make the quarterly board reports more accurate. reporter.apache.org provides the number of emails received on the list during the quarter. In my view, having the GitHub, Jira, Jenkins, etc emails on the dev list skews things as they dominate they number of “real” discussion emails

Re: [Log4j] Next release?

Please do work on Chainsaw. Of course, that isn’t related to a Log4j release (or vice versa). Ralph > On Oct 12, 2017, at 1:53 PM, Matt Sicker wrote: > > I almost forgot that I have my properties simplification branch still > waiting to merge. I should be able to get to that this weekend as I'

Re: Logging list for emails generated by tools

If it makes email filter rules easier to configure, I'd say go for it. It'd be just like the commits@ list though with floods of emails coming in every so often that I just have to skip over (e.g., rebasing a long lived branch). On 12 October 2017 at 15:45, Gary Gregory wrote: > I do not care ei

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202609#comment-16202609 ] Neil Bartlett commented on LOG4J2-2056: --- Joining this thread as I see my name being

Re: [Log4j] Next release?

I almost forgot that I have my properties simplification branch still waiting to merge. I should be able to get to that this weekend as I'd also like to investigate how hard it is to cut an RC for Chainsaw as well. On 12 October 2017 at 15:02, Ralph Goers wrote: > I have a number of issues I hav

Re: Logging list for emails generated by tools

I do not care either way. Gary On Thu, Oct 12, 2017 at 2:34 PM, 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

Logging list for emails generated by tools

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 emails are generated. I would also say that we expect every committe

Re: [Log4j] Next release?

I have a number of issues I have grabbed. I need to look through them and see what I can do. However, I want to get the Automatic-Module-Name headers in. I’ve done the work but am waiting to finalize what the names should be based on Stephen Colbourne’s recommendations. Ralph > On Oct 12, 201

[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&focusedCommentId=16202534#comment-16202534 ] Jorge Sanchez commented on LOG4J2-2062: --- Thank you for your comments I really appre

Re: [Log4j] Next release?

Is there any ongoing work that we want to wait for? I would like to do these: - https://issues.apache.org/jira/browse/LOG4J2-2062 (waiting for contributor to update his PR, will do it myself soon if he doesn't respond timey) - https://issues.apache.org/jira/browse/LOG4J2-2069 (looks quite se

Re: [Log4j] skipJansi by default

My preference is to leave it as. The 2nd option is to add jansi=true|false to the ConsoleAppender. Gary On Oct 12, 2017 13:17, "Mikael Ståldal" wrote: > Do we want to do this? > > https://github.com/apache/logging-log4j2/pull/29 > > (I rather not do this, since I do not use Windows.) >

[Log4j] skipJansi by default

Do we want to do this? https://github.com/apache/logging-log4j2/pull/29 (I rather not do this, since I do not use Windows.)

Re: [Log4j] Next release?

as soon as you can RM ;-) :-) Gary On Oct 12, 2017 13:12, "Mikael Ståldal" wrote: Some users are eager to get access to some newly added features: https://github.com/apache/logging-log4j2/pull/110 When do we plan to do a 2.10.0 release?

[Log4j] Next release?

Some users are eager to get access to some newly added features: https://github.com/apache/logging-log4j2/pull/110 When do we plan to do a 2.10.0 release?

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202397#comment-16202397 ] Ralph Goers commented on LOG4J2-2056: - Yes, an empty Automatic-Module-Name. That seem

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202304#comment-16202304 ] Matt Sicker commented on LOG4J2-2072: - Take a look at the TLS/SSL support classes in

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202234#comment-16202234 ] Frank Swanson commented on LOG4J2-2072: --- Would be done already if it weren't for th

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202207#comment-16202207 ] Gary Gregory commented on LOG4J2-2072: -- Thank you for helping out. Please do not for

[jira] [Reopened] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1216: -- > Nested pattern layout options broken > > > K

[jira] [Commented] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202165#comment-16202165 ] Stephen Colebourne commented on LOG4J2-2056: 1. Do you mean having an empty A

[jira] [Commented] (LOG4J2-2072) Support TLS configuration through FlumeAppender

[ https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202061#comment-16202061 ] Frank Swanson commented on LOG4J2-2072: --- I will put it together shortly(Hopefully t

[jira] [Comment Edited] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201806#comment-16201806 ] Georg Friedrich edited comment on LOG4J2-1216 at 10/12/17 11:23 AM: ---

[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201806#comment-16201806 ] Georg Friedrich commented on LOG4J2-1216: - Hi guys, you just introduced an endles

[jira] [Commented] (LOG4J2-1216) Nested pattern layout options broken

[ https://issues.apache.org/jira/browse/LOG4J2-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201802#comment-16201802 ] ASF GitHub Bot commented on LOG4J2-1216: GitHub user GFriedrich opened a pull req

[GitHub] logging-log4j2 pull request #116: [LOG4J2-1216] fix PatternParser for patter...

GitHub user GFriedrich opened a pull request: https://github.com/apache/logging-log4j2/pull/116 [LOG4J2-1216] fix PatternParser for patterns without closing brackets This fixes an endless parsing for broken patterns without closing brackets like "%d{" or patterns where closing brack

[jira] [Commented] (LOG4J2-1982) Log4j-config.xsd only allows one AppenderRef element for each Logger element

[ https://issues.apache.org/jira/browse/LOG4J2-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201746#comment-16201746 ] Patrick Lucas commented on LOG4J2-1982: --- Shouldn't this have {{minOccurs="0"}} sinc