[jira] [Work logged] (LOG4J2-2600) Declarative Groovy Configuration DSL

[ https://issues.apache.org/jira/browse/LOG4J2-2600?focusedWorklogId=388047&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388047 ] ASF GitHub Bot logged work on LOG4J2-2600: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers commented on issue #274: [LOG4J2-2600] Add declarative Groovy configuration DSL

rgoers commented on issue #274: [LOG4J2-2600] Add declarative Groovy configuration DSL URL: https://github.com/apache/logging-log4j2/pull/274#issuecomment-586678946 Anything going on here or should it be closed? This is an au

[GitHub] [logging-log4j2] rgoers closed pull request #159: [LOG4J2-1013][Lookups] Allow variables with dashes

rgoers closed pull request #159: [LOG4J2-1013][Lookups] Allow variables with dashes URL: https://github.com/apache/logging-log4j2/pull/159 This is an automated message from the Apache Git Service. To respond to the message,

[jira] [Work logged] (LOG4J2-1013) Log4j2 Main Arguments Lookup by name doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-1013?focusedWorklogId=388045&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388045 ] ASF GitHub Bot logged work on LOG4J2-1013: -- Author: ASF GitHub Bot

[jira] [Work logged] (LOG4J2-1013) Log4j2 Main Arguments Lookup by name doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-1013?focusedWorklogId=388046&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388046 ] ASF GitHub Bot logged work on LOG4J2-1013: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers commented on issue #159: [LOG4J2-1013][Lookups] Allow variables with dashes

rgoers commented on issue #159: [LOG4J2-1013][Lookups] Allow variables with dashes URL: https://github.com/apache/logging-log4j2/pull/159#issuecomment-586678868 Closing this as a fix has been committed to allow keys with leading dashes to be escaped. --

[GitHub] [logging-log4j2] rgoers closed pull request #146: fixes capitalization of log4j2.ContextDataInjector property name in Documentation

rgoers closed pull request #146: fixes capitalization of log4j2.ContextDataInjector property name in Documentation URL: https://github.com/apache/logging-log4j2/pull/146 This is an automated message from the Apache Git Servi

[GitHub] [logging-log4j2] rgoers commented on issue #146: fixes capitalization of log4j2.ContextDataInjector property name in Documentation

rgoers commented on issue #146: fixes capitalization of log4j2.ContextDataInjector property name in Documentation URL: https://github.com/apache/logging-log4j2/pull/146#issuecomment-586678672 Closing this per Matt's comments.

[GitHub] [logging-log4j2] rgoers closed pull request #25: LOG4J2-1301 added optionalMonitorFiles attribute for automatic reconf…

rgoers closed pull request #25: LOG4J2-1301 added optionalMonitorFiles attribute for automatic reconf… URL: https://github.com/apache/logging-log4j2/pull/25 This is an automated message from the Apache Git Service. To respon

[GitHub] [logging-log4j2] rgoers commented on issue #25: LOG4J2-1301 added optionalMonitorFiles attribute for automatic reconf…

rgoers commented on issue #25: LOG4J2-1301 added optionalMonitorFiles attribute for automatic reconf… URL: https://github.com/apache/logging-log4j2/pull/25#issuecomment-586678599 Closing this since it has been replaced with Composite Configurations.

[jira] [Closed] (LOG4J2-1301) Automatic reconfiguration with xml and xinclude

[ https://issues.apache.org/jira/browse/LOG4J2-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1301. --- Resolution: Won't Fix Seeing as this can already be accomplished without an XML specific implementa

[GitHub] [logging-log4j2] rgoers closed pull request #144: [LOG4J2-2211] Update StrSubstitutor.java

rgoers closed pull request #144: [LOG4J2-2211] Update StrSubstitutor.java URL: https://github.com/apache/logging-log4j2/pull/144 This is an automated message from the Apache Git Service. To respond to the message, please log

[jira] [Work logged] (LOG4J2-2211) MainMapLookup ${main:--file} placeholder doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-2211?focusedWorklogId=388041&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388041 ] ASF GitHub Bot logged work on LOG4J2-2211: -- Author: ASF GitHub Bot

[jira] [Work logged] (LOG4J2-2211) MainMapLookup ${main:--file} placeholder doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-2211?focusedWorklogId=388044&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388044 ] ASF GitHub Bot logged work on LOG4J2-2211: -- Author: ASF GitHub Bot

[jira] [Work logged] (LOG4J2-2211) MainMapLookup ${main:--file} placeholder doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-2211?focusedWorklogId=388042&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388042 ] ASF GitHub Bot logged work on LOG4J2-2211: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers commented on issue #144: [LOG4J2-2211] Update StrSubstitutor.java

rgoers commented on issue #144: [LOG4J2-2211] Update StrSubstitutor.java URL: https://github.com/apache/logging-log4j2/pull/144#issuecomment-586678370 Closing this PR. The issue was fixed a different way. This is an automated

[jira] [Work logged] (LOG4J2-2211) MainMapLookup ${main:--file} placeholder doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-2211?focusedWorklogId=388043&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388043 ] ASF GitHub Bot logged work on LOG4J2-2211: -- Author: ASF GitHub Bot

[jira] [Comment Edited] (LOG4J2-2211) MainMapLookup ${main:--file} placeholder doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037735#comment-17037735 ] Ralph Goers edited comment on LOG4J2-2211 at 2/16/20 7:44 AM:

[GitHub] [logging-log4j2] rgoers commented on issue #145: fix bug LOG4J2-2211

rgoers commented on issue #145: fix bug LOG4J2-2211 URL: https://github.com/apache/logging-log4j2/pull/145#issuecomment-586678335 Closing this PR. The issue was fixed a different way. This is an automated message from the Apa

[GitHub] [logging-log4j2] rgoers closed pull request #145: fix bug LOG4J2-2211

rgoers closed pull request #145: fix bug LOG4J2-2211 URL: https://github.com/apache/logging-log4j2/pull/145 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[jira] [Comment Edited] (LOG4J2-2211) MainMapLookup ${main:--file} placeholder doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037735#comment-17037735 ] Ralph Goers edited comment on LOG4J2-2211 at 2/16/20 7:41 AM:

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

See Changes: [rgoers] LOG4J2-2211 - Allow Lookup keys with leading dashes by using a slash as -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node envir

[jira] [Resolved] (LOG4J2-2211) MainMapLookup ${main:--file} placeholder doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2211. - Fix Version/s: 2.13.1 Resolution: Fixed This issue has been resolved by adding support fo

[jira] [Commented] (LOG4J2-2211) MainMapLookup ${main:--file} placeholder doesn't work

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

[jira] [Commented] (LOG4J2-2211) MainMapLookup ${main:--file} placeholder doesn't work

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

Jenkins build is still unstable: Log4j2Windows #47

See

Jenkins build is still unstable: Log4j2Windows #46

See

[jira] [Commented] (LOG4J2-2782) Use LinkedBlockingQueue instead of synchronized collection in StatusConfiguration

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

[GitHub] [logging-log4j2] rgoers closed pull request #298: Synchronize before looping over synchronized collection

rgoers closed pull request #298: Synchronize before looping over synchronized collection URL: https://github.com/apache/logging-log4j2/pull/298 This is an automated message from the Apache Git Service. To respond to the mess

[jira] [Commented] (LOG4J2-2782) Use LinkedBlockingQueue instead of synchronized collection in StatusConfiguration

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

[jira] [Closed] (LOG4J2-2782) Use LinkedBlockingQueue instead of synchronized collection in StatusConfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2782. --- Resolution: Fixed > Use LinkedBlockingQueue instead of synchronized collection in > StatusConfigura

[GitHub] [logging-log4j2] rgoers commented on issue #298: Synchronize before looping over synchronized collection

rgoers commented on issue #298: Synchronize before looping over synchronized collection URL: https://github.com/apache/logging-log4j2/pull/298#issuecomment-586655233 An alternative change was made This is an automated message

Jenkins build is still unstable: Log4j2Windows #45

See

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

See

[jira] [Created] (LOG4J2-2782) Use LinkedBlockingQueue instead of synchronized collection in StatusConfiguration

Ralph Goers created LOG4J2-2782: --- Summary: Use LinkedBlockingQueue instead of synchronized collection in StatusConfiguration Key: LOG4J2-2782 URL: https://issues.apache.org/jira/browse/LOG4J2-2782 Proje

Jenkins build is still unstable: Log4j2Windows #44

See

[jira] [Closed] (LOG4J2-2781) ServletContainerInitializer gets the StatusLogger too early.

[ https://issues.apache.org/jira/browse/LOG4J2-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2781. --- Resolution: Fixed > ServletContainerInitializer gets the StatusLogger too early. > -

[jira] [Commented] (LOG4J2-2781) ServletContainerInitializer gets the StatusLogger too early.

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

[jira] [Commented] (LOG4J2-2781) ServletContainerInitializer gets the StatusLogger too early.

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

[jira] [Created] (LOG4J2-2781) ServletContainerInitializer gets the StatusLogger too early.

Ralph Goers created LOG4J2-2781: --- Summary: ServletContainerInitializer gets the StatusLogger too early. Key: LOG4J2-2781 URL: https://issues.apache.org/jira/browse/LOG4J2-2781 Project: Log4j 2

[GitHub] [logging-log4j2] rgoers merged pull request #300: call #StatusLogger.getLogger() only when it's needed.

rgoers merged pull request #300: call #StatusLogger.getLogger() only when it's needed. URL: https://github.com/apache/logging-log4j2/pull/300 This is an automated message from the Apache Git Service. To respond to the messag

[jira] [Work logged] (LOG4J2-1192) Dynamic Subject for SMTP Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1192?focusedWorklogId=388007&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388007 ] ASF GitHub Bot logged work on LOG4J2-1192: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers commented on issue #308: LOG4J2-1192 (support dynamic Subject)

rgoers commented on issue #308: LOG4J2-1192 (support dynamic Subject) URL: https://github.com/apache/logging-log4j2/pull/308#issuecomment-586649722 Still waiting for a response . This is an automated message from the Apache Gi

[jira] [Resolved] (LOG4J2-2676) Backport PluginProcessor use of javax.annotation.processing.Messager to 2.12.x/2.13

[ https://issues.apache.org/jira/browse/LOG4J2-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2676. - Resolution: Fixed Patch to PluginProcessor was manually applied. I did not include the Bazel st

[jira] [Commented] (LOG4J2-2676) Backport PluginProcessor use of javax.annotation.processing.Messager to 2.12.x/2.13

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

[GitHub] [logging-log4j2] rgoers commented on issue #301: LOG4J-2676: Backport use of javax.annotation.processing.Messager to release-2.x.

rgoers commented on issue #301: LOG4J-2676: Backport use of javax.annotation.processing.Messager to release-2.x. URL: https://github.com/apache/logging-log4j2/pull/301#issuecomment-586649599 I committed the change without the bazel stuff. ---

[GitHub] [logging-log4j2] rgoers closed pull request #301: LOG4J-2676: Backport use of javax.annotation.processing.Messager to release-2.x.

rgoers closed pull request #301: LOG4J-2676: Backport use of javax.annotation.processing.Messager to release-2.x. URL: https://github.com/apache/logging-log4j2/pull/301 This is an automated message from the Apache Git Servic

[jira] [Commented] (LOG4J2-2760) RollingFileAppender with DirectWriteRolloverStrategy does not work with HtmlLayout

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

Jenkins build is still unstable: Log4j 2 3.x #537

See

Jenkins build is still unstable: Log4j2Windows #43

See

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

See

[GitHub] [logging-log4j2] rgoers merged pull request #338: use 'final' modifier for fields where possible

rgoers merged pull request #338: use 'final' modifier for fields where possible URL: https://github.com/apache/logging-log4j2/pull/338 This is an automated message from the Apache Git Service. To respond to the message, pleas

[jira] [Resolved] (LOG4J2-2703) MapMessage#getFormattedMessage() incorrectly formats Object's

[ https://issues.apache.org/jira/browse/LOG4J2-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2703. - Fix Version/s: 2.13.1 Resolution: Fixed Patch applied to both release-2.x and master. Ple

[jira] [Commented] (LOG4J2-2703) MapMessage#getFormattedMessage() incorrectly formats Object's

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

[jira] [Commented] (LOG4J2-2703) MapMessage#getFormattedMessage() incorrectly formats Object's

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

[jira] [Commented] (LOG4J2-2703) MapMessage#getFormattedMessage() incorrectly formats Object's

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

[jira] [Work logged] (LOG4J2-2703) MapMessage#getFormattedMessage() incorrectly formats Object's

[ https://issues.apache.org/jira/browse/LOG4J2-2703?focusedWorklogId=387988&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-387988 ] ASF GitHub Bot logged work on LOG4J2-2703: -- Author: ASF GitHub Bot

[jira] [Commented] (LOG4J2-2703) MapMessage#getFormattedMessage() incorrectly formats Object's

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

[GitHub] [logging-log4j2] rgoers merged pull request #339: LOG4J2-2703 Complex data type support in MapMessage JSON formatter

rgoers merged pull request #339: LOG4J2-2703 Complex data type support in MapMessage JSON formatter URL: https://github.com/apache/logging-log4j2/pull/339 This is an automated message from the Apache Git Service. To respond

[jira] [Updated] (LOG4J2-2766) TimeBasedTriggeringPolicy of RollingRandomAccessFile is not updated instantly

[ https://issues.apache.org/jira/browse/LOG4J2-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-2766: Component/s: Reconfiguration > TimeBasedTriggeringPolicy of RollingRandomAccessFile is not updated