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

I guess it was changed from getPid() to pid() after 156. I will have to see if Jenkins has a newer release. Sent from my iPad > On Aug 20, 2017, at 7:51 PM, Apache Jenkins Server > wrote: > > See > > > Changes: >

Re: Logger names for nested classes

Ok, let's document this clearly though. There may be users that have configuration to route logging from an inner class to a separate appender. If I'm not mistaken our change will break such configurations. Also: does Class.getCanonicalName() preserve the trailing $ in Scala classes? (Shamel

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

Yes, renamed in build 166 apparently. https://bugs.openjdk.java.net/browse/JDK-8178347 On Mon, Aug 21, 2017 at 13:40 Remko Popma wrote: > Jenkins may be using an old Java 9: > > JDK[/home/jenkins/tools/java/jigsaw-jdk-9-ea-b156] > > Also, it seems this method was previously called `getPid`. It

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

Jenkins may be using an old Java 9: JDK[/home/jenkins/tools/java/jigsaw-jdk-9-ea-b156] Also, it seems this method was previously called `getPid`. It must have been renamed recently. http://www.javaworld.com/article/3176874/java-language/java-9s-other-new-enhancements-part-3.html On Mon, Aug 21,

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

I don’t understand why this is failing. My local machine is running build 174. Was ProcessHandle.pid() really added that late? Ralph > On Aug 20, 2017, at 7:51 PM, Apache Jenkins Server > wrote: > > See > > > Cha

[jira] [Comment Edited] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134684#comment-16134684 ] Ralph Goers edited comment on LOG4J2-1086 at 8/21/17 4:05 AM: -

[jira] [Commented] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134684#comment-16134684 ] Ralph Goers commented on LOG4J2-1086: - Perrick, The creates 100 Excectuors on 32 thr

Build failed in Jenkins: Log4j 2.x #3005

See Changes: [rgoers] Add missing license header. Message should implement -- Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables

[jira] [Resolved] (LOG4J2-2022) RFC5424Layout should obtain the process id.

[ https://issues.apache.org/jira/browse/LOG4J2-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2022. - Resolution: Fixed > RFC5424Layout should obtain the process id. > ---

[jira] [Closed] (LOG4J2-2022) RFC5424Layout should obtain the process id.

[ https://issues.apache.org/jira/browse/LOG4J2-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2022. --- > RFC5424Layout should obtain the process id. > --- > >

Build failed in Jenkins: Log4j 2.x #3004

See Changes: [rgoers] LOG4J2-2022 - RFC5424Layout now prints the process id -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on u

[jira] [Commented] (LOG4J2-2022) RFC5424Layout should obtain the process id.

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

[jira] [Created] (LOG4J2-2022) RFC5424Layout should obtain the process id.

Ralph Goers created LOG4J2-2022: --- Summary: RFC5424Layout should obtain the process id. Key: LOG4J2-2022 URL: https://issues.apache.org/jira/browse/LOG4J2-2022 Project: Log4j 2 Issue Type: Impro

Build failed in Jenkins: Log4j 2.x #3003

See Changes: [rgoers] Link to Scala site -- [...truncated 4.72 MB...] Uploaded: https://repository.apache.org/content/repositories/snapshots/org/apache/logging/log4j/log4j-nos

[GitHub] logging-log4net issue #14: Add .NET Standard 2.0 build

Github user dpsenner commented on the issue: https://github.com/apache/logging-log4net/pull/14 I'm pleased to say that I was able to merge large parts of your work into the branch `feature/netstandard-2.0` and the build passed. Unfortunately the tests are currently not run because I w

Scala web site

The Scala web site is now published at http://logging.apache.org/log4j/scala/index.html . I have modified it to use the generic Log4j 2 logo instead of the one for Log4j 2 2.7. I see 3 options for linking to the site: 1. Add a link to the Log4j