[jira] [Updated] (LOG4J2-1841) Problems with consequences after LOG4J2-248

[ https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Seweryn Habdank-Wojewodzki updated LOG4J2-1841: --- Description: Situation till Log4j v. 2.5 (including it): 1. One

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

We had once the discussion that we wanted all Apache Logging projects to become very similar in their usage, starting with the same or a very similar configuration. Given that we should aim towards one Apache Logging specification and several Apache Logging specification implementations in the

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

I think that a vast majority of our users only uses one of the languages we support, and therefore only are interested in one of the subprojects. On Fri, Mar 10, 2017 at 11:23 AM, Dominik Psenner wrote: > We had once the discussion that we wanted all Apache Logging projects

[jira] [Created] (LOG4J2-1844) Not the correct value of the month in the log

Vasiliy Ponomarenko created LOG4J2-1844: --- Summary: Not the correct value of the month in the log Key: LOG4J2-1844 URL: https://issues.apache.org/jira/browse/LOG4J2-1844 Project: Log4j 2

[jira] [Created] (LOG4J2-1845) Handle when LogEvent.getLoggerName() returns null in KafkaAppender

Mikael Ståldal created LOG4J2-1845: -- Summary: Handle when LogEvent.getLoggerName() returns null in KafkaAppender Key: LOG4J2-1845 URL: https://issues.apache.org/jira/browse/LOG4J2-1845 Project:

[jira] [Created] (LOG4J2-1847) Handle when LogEvent.getLoggerName() returns null in LoggerPatternConverter

Mikael Ståldal created LOG4J2-1847: -- Summary: Handle when LogEvent.getLoggerName() returns null in LoggerPatternConverter Key: LOG4J2-1847 URL: https://issues.apache.org/jira/browse/LOG4J2-1847

[jira] [Created] (LOG4J2-1846) Handle when LogEvent.getLoggerName() returns null in LoggerNameLevelRewritePolicy

Mikael Ståldal created LOG4J2-1846: -- Summary: Handle when LogEvent.getLoggerName() returns null in LoggerNameLevelRewritePolicy Key: LOG4J2-1846 URL: https://issues.apache.org/jira/browse/LOG4J2-1846

[jira] [Resolved] (LOG4J2-1845) Handle when LogEvent.getLoggerName() returns null in KafkaAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1845. Resolution: Fixed Fix Version/s: 2.8.2 In Git master. > Handle when

[jira] [Updated] (LOG4J2-1847) Handle when LogEvent.getLoggerName() returns null in LoggerPatternConverter

[ https://issues.apache.org/jira/browse/LOG4J2-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1847: --- Priority: Minor (was: Major) > Handle when LogEvent.getLoggerName() returns null in

[jira] [Resolved] (LOG4J2-1846) Handle when LogEvent.getLoggerName() returns null in LoggerNameLevelRewritePolicy

[ https://issues.apache.org/jira/browse/LOG4J2-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1846. Resolution: Fixed Fix Version/s: 2.8.2 In Git master. > Handle when

[jira] [Commented] (LOG4J2-1847) Handle when LogEvent.getLoggerName() returns null in LoggerPatternConverter

[ https://issues.apache.org/jira/browse/LOG4J2-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905089#comment-15905089 ] Mikael Ståldal commented on LOG4J2-1847: Not obvious how to fix this one. > Handle when

[jira] [Commented] (LOG4J2-1845) Handle when LogEvent.getLoggerName() returns null in KafkaAppender

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

[jira] [Commented] (LOG4J2-1845) Handle when LogEvent.getLoggerName() returns null in KafkaAppender

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

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

This is exactly why we need one dev list. These last two responses dropped the other lists. This is a horrible way to have discussions that affect all the sub projects. Ralph > On Mar 10, 2017, at 9:11 AM, Matt Sicker wrote: > > I'd love to see more unified configurations

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

Total agreement. On 10 Mar 2017 6:26 p.m., "Ralph Goers" wrote: > This is exactly why we need one dev list. These last two responses dropped > the other lists. This is a horrible way to have discussions that affect > all the sub projects. > > Ralph > > > On Mar 10,

[jira] [Resolved] (LOG4J2-1844) Not the correct value of the month in the log

[ https://issues.apache.org/jira/browse/LOG4J2-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1844. - Resolution: Not A Problem I believe the specified pattern is wrong and should be {{

[jira] [Updated] (LOG4J2-1844) Not the correct value of the month in the log

[ https://issues.apache.org/jira/browse/LOG4J2-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1844: Description: if pattern contains Month like {{%d\{-mm-dd HH:mm:ss.SSS\}}} log has wrong Month

[jira] [Assigned] (LOG4J2-1844) Not the correct value of the month in the log

[ https://issues.apache.org/jira/browse/LOG4J2-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1844: --- Assignee: Remko Popma > Not the correct value of the month in the log >

[jira] [Comment Edited] (LOG4J2-1844) Not the correct value of the month in the log

[ https://issues.apache.org/jira/browse/LOG4J2-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905468#comment-15905468 ] Remko Popma edited comment on LOG4J2-1844 at 3/10/17 5:46 PM: -- I believe the

Re: [Discuss][VOTE] Combine the project user and dev mailing lists into user@ and dev@

I'd love to see more unified configurations in all the subprojects. Gary mentioned that as an idea for log4cxx as that would make it useful for his use case where they're using both Java and C++ in various projects. While the programming languages in use here (Java, .NET, PHP, and C++) aren't

[jira] [Commented] (LOG4J2-1841) Problems with consequences after LOG4J2-248

[ https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905285#comment-15905285 ] Matt Sicker commented on LOG4J2-1841: - The component properties file is a way to override system

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #33

See Changes: [mikael.staldal] LOG4J2-1845 Handle when LogEvent.getLoggerName() returns null in [mikael.staldal] LOG4J2-1845

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #33

See Changes: [mikael.staldal] LOG4J2-1845 Handle when LogEvent.getLoggerName() returns null in [mikael.staldal] LOG4J2-1845