Log4j 2.9

I’d like to start the release process next weekend for Log4j 2.9. I believe there is some web site work that has to take place for that to happen to integrate with the new Scala release. Has Scala been published to the web site? I can’t find it in SVN. Ralph

[jira] [Updated] (LOG4J2-2009) Rolling appender managers broken on pattern/policy reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leliel Trethowen updated LOG4J2-2009: - Description: LOG4J2-1964 is not fixed. Not fixed per latest snapshot at:

[jira] [Reopened] (LOG4J2-2009) Rolling appender managers broken on pattern/policy reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leliel Trethowen reopened LOG4J2-2009: -- Corrected replication case. > Rolling appender managers broken on pattern/policy

[jira] [Commented] (LOG4J2-1964) Dynamic reconfiguration does not work for filePattern of RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125260#comment-16125260 ] Ralph Goers commented on LOG4J2-1964: - See LOG4J2-2009. The test above is invalid. > Dynamic

[jira] [Resolved] (LOG4J2-2009) Rolling appender managers broken on pattern/policy reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2009. - Resolution: Invalid Actually, the stack trace above proves the LOG4J2-1964 is fixed. You are

[jira] [Updated] (LOG4J2-2009) Rolling appender managers broken on pattern/policy reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leliel Trethowen updated LOG4J2-2009: - Description: LOG4J2-1964 is not fixed. Not fixed per latest snapshot at:

[jira] [Created] (LOG4J2-2009) Rolling appender managers broken on pattern/policy reconfiguration

Leliel Trethowen created LOG4J2-2009: Summary: Rolling appender managers broken on pattern/policy reconfiguration Key: LOG4J2-2009 URL: https://issues.apache.org/jira/browse/LOG4J2-2009 Project:

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

See

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

See

[jira] [Commented] (LOG4J2-2008) RFC5424Layout should support multiple StructuredData elements.

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

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

See

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

See

[jira] [Commented] (LOG4J2-2008) RFC5424Layout should support multiple StructuredData elements.

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

[jira] [Commented] (LOG4J2-2008) RFC5424Layout should support multiple StructuredData elements.

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

[jira] [Created] (LOG4J2-2008) RFC5424Layout should support multiple StructuredData elements.

Ralph Goers created LOG4J2-2008: --- Summary: RFC5424Layout should support multiple StructuredData elements. Key: LOG4J2-2008 URL: https://issues.apache.org/jira/browse/LOG4J2-2008 Project: Log4j 2

Re: Logger names for nested classes

Recapping: Using it: wrote: > Yes, that is the way I would envision it. The default would be how it > works now. > > Ralph > > > On Aug 13, 2017, at 12:37 PM, Gary Gregory > wrote: > > > > Well we can make an exception for trailing $? > > > > Do we want to add an

Re: Logger names for nested classes

Sure why not. I just want to nail down the spec before we get caught up in implementation details. Gary On Aug 13, 2017 13:53, "Dominik Psenner" wrote: > What about a LoggerHierarchySeparationStrategy interface along with a > default impl? > > On 13 Aug 2017 9:37 p.m.,

Re: Logger names for nested classes

Well we can make an exception for trailing $? Do we want to add an attribute in the Configuration XML element? For example hierarchySeparators=".$/" What should the default be? Gary On Aug 13, 2017 12:17, "Matt Sicker" wrote: > Having the dollar sign interpreted differently

Re: Logger names for nested classes

Having the dollar sign interpreted differently also makes a difference in Scala classes and potentially other languages. For example, in Scala, an "object" class is a singleton instance of the class (vaguely similar to a class with all static methods and fields), and it's translated to a Java

Re: Logger names for nested classes

You cannot replace. We always must support dots. But some people have asked for '/' as well. Sent from my iPad > On Aug 13, 2017, at 8:38 AM, Dominik Psenner wrote: > > Yes > >> On 13 Aug 2017 5:13 p.m., "Gary Gregory" wrote: >> >> You are

Re: Logger names for nested classes

You are talking about replacing $ with dot in the getLogger(Class) API? Gary On Aug 13, 2017 01:57, "Dominik Psenner" wrote: > Could the $ be replaced by a dot when the logger is instantiated? Log4net > picks the class name as logger name but also allows custom logger

Re: Logger names for nested classes

Rather than implementing this I would rather have the separator chars be specifiable in the configuration. Blatantly making this change might cause compatibility problems, although I am not really sure how it could. Ralph > On Aug 12, 2017, at 11:29 AM, Gary Gregory