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

See Changes: [ckozak] Fix LOG4J2-2735 issue reference, previously missing '2' -- [...truncated 739.25 KB...] [WARNING]

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

See Changes: [ckozak] LOG4J-2735 - make PluginCache output reproducible (#321) [ckozak] LOG4J-2735 changelog -- [...truncated 739.53 KB...] [WARNING]

[jira] [Resolved] (LOG4J2-2735) Make the content of the generated log4j2plugins.dat file repeatable

[ https://issues.apache.org/jira/browse/LOG4J2-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2735. -- Fix Version/s: 2.13.1 Resolution: Fixed I've merged the fix into release-2.x and master

[jira] [Commented] (LOG4J2-2735) Make the content of the generated log4j2plugins.dat file repeatable

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

[jira] [Commented] (LOG4J2-2735) Make the content of the generated log4j2plugins.dat file repeatable

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

[GitHub] [logging-log4j2] carterkozak merged pull request #321: LOG4J-2735 - make PluginCache output reproducible

carterkozak merged pull request #321: LOG4J-2735 - make PluginCache output reproducible URL: https://github.com/apache/logging-log4j2/pull/321 This is an automated message from the Apache Git Service. To respond to the messa

[jira] [Commented] (LOG4J2-2735) Make the content of the generated log4j2plugins.dat file repeatable

[ https://issues.apache.org/jira/browse/LOG4J2-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17003038#comment-17003038 ] Carter Kozak commented on LOG4J2-2735: -- Thanks for filing this, I have a few large

[jira] [Closed] (LOG4J2-2748) Add an alternative to FixedDateFormat.ISO8601_PERIOD with microsecond precision

[ https://issues.apache.org/jira/browse/LOG4J2-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2748. Verified with test coverage. > Add an alternative to FixedDateFormat.ISO8601_PERIOD with microsecond

[jira] [Commented] (LOG4J2-2748) Add an alternative to FixedDateFormat.ISO8601_PERIOD with microsecond precision

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

[jira] [Commented] (LOG4J2-2748) Add an alternative to FixedDateFormat.ISO8601_PERIOD with microsecond precision

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

[jira] [Resolved] (LOG4J2-2748) Add an alternative to FixedDateFormat.ISO8601_PERIOD with microsecond precision

[ https://issues.apache.org/jira/browse/LOG4J2-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2748. -- Resolution: Fixed > Add an alternative to FixedDateFormat.ISO8601_PERIOD with microsecond > p

[jira] [Created] (LOG4J2-2748) Add an alternative to FixedDateFormat.ISO8601_PERIOD with microsecond precision

Carter Kozak created LOG4J2-2748: Summary: Add an alternative to FixedDateFormat.ISO8601_PERIOD with microsecond precision Key: LOG4J2-2748 URL: https://issues.apache.org/jira/browse/LOG4J2-2748 Proje

[jira] [Assigned] (LOG4J2-2748) Add an alternative to FixedDateFormat.ISO8601_PERIOD with microsecond precision

[ https://issues.apache.org/jira/browse/LOG4J2-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2748: Assignee: Carter Kozak > Add an alternative to FixedDateFormat.ISO8601_PERIOD with micros

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

See

Build failed in Jenkins: Log4j 2 2.x #4068

See Changes: [ckozak] LOG4J2-2739: Fix erroneous log4j-jul recursive logger detection -- [...truncated 1.23 MB...] Uploading to apache.snapshots.https: https://repository

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

See

[GitHub] [logging-log4j2] carterkozak commented on issue #325: LOG4J2-2745: LOG4J2-2744: Upgrade slf4j-1.8 to beta4 (from alpha2)

carterkozak commented on issue #325: LOG4J2-2745: LOG4J2-2744: Upgrade slf4j-1.8 to beta4 (from alpha2) URL: https://github.com/apache/logging-log4j2/pull/325#issuecomment-568773010 merged This is an automated message from th

[jira] [Commented] (LOG4J2-2739) Combination of async logging and log4j-jul results in recursive call warnings

[ https://issues.apache.org/jira/browse/LOG4J2-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002916#comment-17002916 ] Carter Kozak commented on LOG4J2-2739: -- I'm planning to test from a snapshot where

[GitHub] [logging-log4j2] carterkozak closed pull request #325: LOG4J2-2745: LOG4J2-2744: Upgrade slf4j-1.8 to beta4 (from alpha2)

carterkozak closed pull request #325: LOG4J2-2745: LOG4J2-2744: Upgrade slf4j-1.8 to beta4 (from alpha2) URL: https://github.com/apache/logging-log4j2/pull/325 This is an automated message from the Apache Git Service. To res

[jira] [Resolved] (LOG4J2-2739) Combination of async logging and log4j-jul results in recursive call warnings

[ https://issues.apache.org/jira/browse/LOG4J2-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2739. -- Resolution: Fixed > Combination of async logging and log4j-jul results in recursive call warni

[jira] [Commented] (LOG4J2-2739) Combination of async logging and log4j-jul results in recursive call warnings

[ https://issues.apache.org/jira/browse/LOG4J2-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002914#comment-17002914 ] Carter Kozak commented on LOG4J2-2739: -- > In this current case we also need to make

[jira] [Commented] (LOG4J2-2739) Combination of async logging and log4j-jul results in recursive call warnings

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

[jira] [Commented] (LOG4J2-2739) Combination of async logging and log4j-jul results in recursive call warnings

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

[jira] [Updated] (LOG4J2-2739) Combination of async logging and log4j-jul results in recursive call warnings

[ https://issues.apache.org/jira/browse/LOG4J2-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2739: - Fix Version/s: 2.13.1 > Combination of async logging and log4j-jul results in recursive call war

[jira] [Commented] (LOG4J2-2743) Spring Boot Starters(2.0.8) still refers to log4j2 2.10.0 libraries in Maven Central

[ https://issues.apache.org/jira/browse/LOG4J2-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002908#comment-17002908 ] Ralph Goers commented on LOG4J2-2743: - Log4j cannot build against an SLF4J version n

Jenkins build became unstable: Log4j 2 3.x #508

See

[jira] [Assigned] (LOG4J2-2739) Combination of async logging and log4j-jul results in recursive call warnings

[ https://issues.apache.org/jira/browse/LOG4J2-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2739: Assignee: Carter Kozak > Combination of async logging and log4j-jul results in recursive

[jira] [Commented] (LOG4J2-2743) Spring Boot Starters(2.0.8) still refers to log4j2 2.10.0 libraries in Maven Central

[ https://issues.apache.org/jira/browse/LOG4J2-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002905#comment-17002905 ] Buks van der Lingen commented on LOG4J2-2743: - h2. Compile Dependencies (3)

[jira] [Assigned] (LOG4J2-2746) Change in shutdown behaviour between 2.12.1 and 2.13.0

[ https://issues.apache.org/jira/browse/LOG4J2-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-2746: --- Assignee: Ralph Goers > Change in shutdown behaviour between 2.12.1 and 2.13.0 > --

[jira] [Commented] (LOG4J2-2743) Spring Boot Starters(2.0.8) still refers to log4j2 2.10.0 libraries in Maven Central

[ https://issues.apache.org/jira/browse/LOG4J2-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002904#comment-17002904 ] Ralph Goers commented on LOG4J2-2743: - I have no idea why you posted a portion of th

[jira] [Comment Edited] (LOG4J2-2743) Spring Boot Starters(2.0.8) still refers to log4j2 2.10.0 libraries in Maven Central

[ https://issues.apache.org/jira/browse/LOG4J2-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002733#comment-17002733 ] Ralph Goers edited comment on LOG4J2-2743 at 12/24/19 3:40 PM: ---

[jira] [Updated] (LOG4J2-2747) AsyncLogger should clear RingBufferLogEventTranslator when it's not used

[ https://issues.apache.org/jira/browse/LOG4J2-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2747: - Fix Version/s: 2.13.1 Affects Version/s: 2.13.0 > AsyncLogger should clear RingBufferLog

[jira] [Resolved] (LOG4J2-2747) AsyncLogger should clear RingBufferLogEventTranslator when it's not used

[ https://issues.apache.org/jira/browse/LOG4J2-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2747. -- Resolution: Fixed > AsyncLogger should clear RingBufferLogEventTranslator when it's not used >

[jira] [Closed] (LOG4J2-2747) AsyncLogger should clear RingBufferLogEventTranslator when it's not used

[ https://issues.apache.org/jira/browse/LOG4J2-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2747. Verified in a test > AsyncLogger should clear RingBufferLogEventTranslator when it's not used > -

[jira] [Commented] (LOG4J2-2747) AsyncLogger should clear RingBufferLogEventTranslator when it's not used

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

[jira] [Commented] (LOG4J2-2747) AsyncLogger should clear RingBufferLogEventTranslator when it's not used

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

[jira] [Created] (LOG4J2-2747) AsyncLogger should clear RingBufferLogEventTranslator when it's not used

Carter Kozak created LOG4J2-2747: Summary: AsyncLogger should clear RingBufferLogEventTranslator when it's not used Key: LOG4J2-2747 URL: https://issues.apache.org/jira/browse/LOG4J2-2747 Project: Log

[jira] [Assigned] (LOG4J2-2747) AsyncLogger should clear RingBufferLogEventTranslator when it's not used

[ https://issues.apache.org/jira/browse/LOG4J2-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reassigned LOG4J2-2747: Assignee: Carter Kozak > AsyncLogger should clear RingBufferLogEventTranslator when it's

[jira] [Closed] (LOG4J2-2745) Upgrade slf4j 1.8 dependency to 1.8.0-alpha4

[ https://issues.apache.org/jira/browse/LOG4J2-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2745. > Upgrade slf4j 1.8 dependency to 1.8.0-alpha4 > > >

[jira] [Resolved] (LOG4J2-2744) Log4jLogger.converter can be removed from log4j-slf4j18-impl

[ https://issues.apache.org/jira/browse/LOG4J2-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2744. -- Resolution: Fixed > Log4jLogger.converter can be removed from log4j-slf4j18-impl > ---

[jira] [Closed] (LOG4J2-2744) Log4jLogger.converter can be removed from log4j-slf4j18-impl

[ https://issues.apache.org/jira/browse/LOG4J2-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2744. > Log4jLogger.converter can be removed from log4j-slf4j18-impl > -

[jira] [Resolved] (LOG4J2-2745) Upgrade slf4j 1.8 dependency to 1.8.0-alpha4

[ https://issues.apache.org/jira/browse/LOG4J2-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2745. -- Resolution: Fixed > Upgrade slf4j 1.8 dependency to 1.8.0-alpha4 > ---

[jira] [Commented] (LOG4J2-2745) Upgrade slf4j 1.8 dependency to 1.8.0-alpha4

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

[jira] [Commented] (LOG4J2-2744) Log4jLogger.converter can be removed from log4j-slf4j18-impl

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

[jira] [Commented] (LOG4J2-2744) Log4jLogger.converter can be removed from log4j-slf4j18-impl

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

[jira] [Commented] (LOG4J2-2745) Upgrade slf4j 1.8 dependency to 1.8.0-alpha4

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

[jira] [Updated] (LOG4J2-2746) Change in shutdown behaviour between 2.12.1 and 2.13.0

[ https://issues.apache.org/jira/browse/LOG4J2-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Walker updated LOG4J2-2746: - Description: The attached mavenised example demonstrated the observed behaviour. In essence the

[jira] [Updated] (LOG4J2-2746) Change in shutdown behaviour between 2.12.1 and 2.13.0

[ https://issues.apache.org/jira/browse/LOG4J2-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Walker updated LOG4J2-2746: - Environment: {noformat} Apache Maven 3.6.2; Java version: 11.0.5, vendor: AdoptOpenJDK; Default

[jira] [Updated] (LOG4J2-2746) Change in shutdown behaviour between 2.12.1 and 2.13.0

[ https://issues.apache.org/jira/browse/LOG4J2-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Walker updated LOG4J2-2746: - Environment: {noformat} Apache Maven 3.6.2  Java version: 11.0.5, vendor: AdoptOpenJDK, runtime:

[jira] [Created] (LOG4J2-2746) Change in shutdown behaviour between 2.12.1 and 2.13.0

Brett Walker created LOG4J2-2746: Summary: Change in shutdown behaviour between 2.12.1 and 2.13.0 Key: LOG4J2-2746 URL: https://issues.apache.org/jira/browse/LOG4J2-2746 Project: Log4j 2 Issu

[jira] [Commented] (LOG4J2-2743) Spring Boot Starters(2.0.8) still refers to log4j2 2.10.0 libraries in Maven Central

[ https://issues.apache.org/jira/browse/LOG4J2-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002733#comment-17002733 ] Buks van der Lingen commented on LOG4J2-2743: - org.apache.logging.log4j l