Jenkins build became unstable: Log4j 2 2.x #4059

2019-12-10 Thread Apache Jenkins Server
See

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

2019-12-10 Thread Apache Jenkins Server
See

Build failed in Jenkins: Log4j 2 3.x #501

2019-12-10 Thread Apache Jenkins Server
See Changes: -- Started by user rgoers Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H24 (ubuntu) in workspace

[jira] [Updated] (LOG4J2-2733) the initial logs were flushed away while file rolling at the second time

2019-12-10 Thread ma jun (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ma jun updated LOG4J2-2733: --- Environment: Linux RHEL 6 java 1.8.0_151l64 Linux login session's timezone: EST > the initial logs were

[GitHub] [logging-log4j2] rgoers commented on issue #320: Layouts doc possible fail

2019-12-10 Thread GitBox
rgoers commented on issue #320: Layouts doc possible fail URL: https://github.com/apache/logging-log4j2/pull/320#issuecomment-564206518 After re-reading this I realized the previous text, compact (a.k.a not "pretty"), is correct but confusing. compact does mean the output will not be pr

[GitHub] [logging-log4j2] rgoers merged pull request #320: Layouts doc possible fail

2019-12-10 Thread GitBox
rgoers merged pull request #320: Layouts doc possible fail URL: https://github.com/apache/logging-log4j2/pull/320 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub an

[GitHub] [logging-log4j2] elfogre opened a new pull request #320: Layouts doc possible fail

2019-12-10 Thread GitBox
elfogre opened a new pull request #320: Layouts doc possible fail URL: https://github.com/apache/logging-log4j2/pull/320 Not compact json means pretty style (previous it said not pretty) This is an automated message from the A

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

2019-12-10 Thread Apache Jenkins Server
See

[jira] [Work logged] (LOG4J2-2668) Add support for Scala 2.13

2019-12-10 Thread ASF GitHub Bot (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2668?focusedWorklogId=357215&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-357215 ] ASF GitHub Bot logged work on LOG4J2-2668: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j-scala] JD557 commented on issue #3: add support for scala 2.13.0 [LOG4J2-2668]

2019-12-10 Thread GitBox
JD557 commented on issue #3: add support for scala 2.13.0 [LOG4J2-2668] URL: https://github.com/apache/logging-log4j-scala/pull/3#issuecomment-564110595 @jvz any updates on this? This is an automated message from the Apache Gi

[jira] [Commented] (LOG4J2-2732) Add ThreadContext.putIfNull(String, String)

2019-12-10 Thread Ralph Goers (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992635#comment-16992635 ] Ralph Goers commented on LOG4J2-2732: - You are correct. It seems I manually applied

[jira] [Commented] (LOG4J2-2732) Add ThreadContext.putIfNull(String, String)

2019-12-10 Thread Matt Pavlovich (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992626#comment-16992626 ] Matt Pavlovich commented on LOG4J2-2732: [~rgoers] It looks like the 'release-2.