[GitHub] [logging-log4j2] jvz commented on a change in pull request #305: (doc) Fix typos in documentation

jvz commented on a change in pull request #305: (doc) Fix typos in documentation URL: https://github.com/apache/logging-log4j2/pull/305#discussion_r320051451 ## File path: mypatch.patch ## @@ -0,0 +1,1081 @@ +diff --git a/log4j-core/src/main/java/org/apache/logging/log4j/c

[GitHub] [logging-log4j2] jvz commented on a change in pull request #305: (doc) Fix typos in documentation

jvz commented on a change in pull request #305: (doc) Fix typos in documentation URL: https://github.com/apache/logging-log4j2/pull/305#discussion_r320051471 ## File path: src/site/asciidoc/index.adoc.rej ## @@ -0,0 +1,21 @@ +diff a/src/site/asciidoc/index.adoc b/src/site/a

[jira] [Work logged] (LOG4J2-2678) Add LogEvent timestamp to ProducerRecord in KafkaAppender

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

[GitHub] [logging-log4j2] jvz commented on issue #306: [LOG4J2-2678] Add LogEvent timestamp to Kafka ProducerRecord

jvz commented on issue #306: [LOG4J2-2678] Add LogEvent timestamp to Kafka ProducerRecord URL: https://github.com/apache/logging-log4j2/pull/306#issuecomment-527251648 If you rebase from master, you should get a working Travis config to test this. As for the use case, making the eve

[jira] [Work logged] (LOG4J2-2652) JSON output wrong when using additonal fields

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

[GitHub] [logging-log4j2] jvz commented on issue #307: [LOG4J2-2652] JSON output wrong when using additonal fields

jvz commented on issue #307: [LOG4J2-2652] JSON output wrong when using additonal fields URL: https://github.com/apache/logging-log4j2/pull/307#issuecomment-527251506 If you rebase from master, you should get a working Travis config to test this. --

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

See

[jira] [Resolved] (LOG4J2-2617) Typo in method name org.apache.logging.log4j.core.config.composite.MergeStrategy.mergConfigurations(Node, Node, PluginManager)

[ https://issues.apache.org/jira/browse/LOG4J2-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-2617. - Resolution: Fixed Updated in master. If we want to backport this to 2.x, it can be added as a d

[jira] [Updated] (LOG4J2-2617) Typo in method name org.apache.logging.log4j.core.config.composite.MergeStrategy.mergConfigurations(Node, Node, PluginManager)

[ https://issues.apache.org/jira/browse/LOG4J2-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-2617: Fix Version/s: 3.0.0 > Typo in method name > org.apache.logging.log4j.core.config.composite.Merge

[jira] [Commented] (LOG4J2-2617) Typo in method name org.apache.logging.log4j.core.config.composite.MergeStrategy.mergConfigurations(Node, Node, PluginManager)

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

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

See Changes: [Matt Sicker] Fix javadoc [Matt Sicker] Simplify loader methods [Matt Sicker] Fix typo -- [...truncated 244.00 KB...] (see https://errorprone.info/bugpatt

[jira] [Assigned] (LOG4J2-2617) Typo in method name org.apache.logging.log4j.core.config.composite.MergeStrategy.mergConfigurations(Node, Node, PluginManager)

[ https://issues.apache.org/jira/browse/LOG4J2-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-2617: --- Assignee: Matt Sicker > Typo in method name > org.apache.logging.log4j.core.config.composi

[jira] [Closed] (LOG4J2-2686) Flatten and merge ClassName2-style classes

[ https://issues.apache.org/jira/browse/LOG4J2-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-2686. --- Resolution: Duplicate Whoops, found an open issue for this after viewing git history. > Flatten and

[jira] [Created] (LOG4J2-2686) Flatten and merge ClassName2-style classes

Matt Sicker created LOG4J2-2686: --- Summary: Flatten and merge ClassName2-style classes Key: LOG4J2-2686 URL: https://issues.apache.org/jira/browse/LOG4J2-2686 Project: Log4j 2 Issue Type: Improv

[jira] [Work logged] (LOG4J2-2678) Add LogEvent timestamp to ProducerRecord in KafkaAppender

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

[GitHub] [logging-log4j2] fedexist edited a comment on issue #306: [LOG4J2-2678] Add LogEvent timestamp to Kafka ProducerRecord

fedexist edited a comment on issue #306: [LOG4J2-2678] Add LogEvent timestamp to Kafka ProducerRecord URL: https://github.com/apache/logging-log4j2/pull/306#issuecomment-527152446 I honestly wouldn't know whether there's any _actual_ use case where the producer timestamp (i.e. the current

[jira] [Work logged] (LOG4J2-2678) Add LogEvent timestamp to ProducerRecord in KafkaAppender

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

[GitHub] [logging-log4j2] fedexist commented on issue #306: [LOG4J2-2678] Add LogEvent timestamp to Kafka ProducerRecord

fedexist commented on issue #306: [LOG4J2-2678] Add LogEvent timestamp to Kafka ProducerRecord URL: https://github.com/apache/logging-log4j2/pull/306#issuecomment-527152446 I honestly wouldn't know whether there's any _actual_ use case where the producer timestamp (i.e. the current behavio

[jira] [Work logged] (LOG4J2-2678) Add LogEvent timestamp to ProducerRecord in KafkaAppender

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

[GitHub] [logging-log4j2] garydgregory commented on issue #306: [LOG4J2-2678] Add LogEvent timestamp to Kafka ProducerRecord

garydgregory commented on issue #306: [LOG4J2-2678] Add LogEvent timestamp to Kafka ProducerRecord URL: https://github.com/apache/logging-log4j2/pull/306#issuecomment-527129640 I was asking the OP how it could break, since that person might have domain-specific knowledge I am not aware of.

[jira] [Commented] (LOG4J2-2684) Misleading system property in documentation to make all loggers asynchronous

[ https://issues.apache.org/jira/browse/LOG4J2-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920703#comment-16920703 ] Manuel Ott commented on LOG4J2-2684: Since version 2.10 the property name is 'log4j2