[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request #372: Bump mongodb3.version from 3.12.4 to 3.12.5

dependabot[bot] opened a new pull request #372: URL: https://github.com/apache/logging-log4j2/pull/372 Bumps `mongodb3.version` from 3.12.4 to 3.12.5. Updates `mongodb-driver` from 3.12.4 to 3.12.5 Release notes Sourced from https://github.com/mongodb/mongo-java-driver/releases"

[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request #370: Bump jetty-util from 8.2.0.v20160908 to 9.4.30.v20200611

dependabot[bot] opened a new pull request #370: URL: https://github.com/apache/logging-log4j2/pull/370 Bumps [jetty-util](https://github.com/eclipse/jetty.project) from 8.2.0.v20160908 to 9.4.30.v20200611. Commits https://github.com/eclipse/jetty.project/commit/271836e4c1f4612

[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request #371: Bump jctools-core from 1.2.1 to 3.0.0

dependabot[bot] opened a new pull request #371: URL: https://github.com/apache/logging-log4j2/pull/371 Bumps [jctools-core](https://github.com/JCTools/JCTools) from 1.2.1 to 3.0.0. Release notes Sourced from https://github.com/JCTools/JCTools/releases";>jctools-core's releases.

[CI][FAILURE] log4j/master#88 has potential issues

There is a build failure in log4j/master. Build: https://builds.apache.org/job/log4j/job/master/88/ Logs: https://builds.apache.org/job/log4j/job/master/88/console Test results: https://builds.apache.org/job/log4j/job/master/88/testReport/ Changes: https://builds.apache.org/job/log4j/job/master/8

[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request #369: Bump xmlunit-core from 2.6.2 to 2.7.0

dependabot[bot] opened a new pull request #369: URL: https://github.com/apache/logging-log4j2/pull/369 Bumps [xmlunit-core](https://github.com/xmlunit/xmlunit) from 2.6.2 to 2.7.0. Release notes Sourced from https://github.com/xmlunit/xmlunit/releases";>xmlunit-core's releases.

[GitHub] [logging-log4j2] vy merged pull request #368: enable Dependabot v2

vy merged pull request #368: URL: https://github.com/apache/logging-log4j2/pull/368 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

[GitHub] [logging-log4j2] rgoers commented on pull request #367: avoid initialize 'volatile' fields with default values

rgoers commented on pull request #367: URL: https://github.com/apache/logging-log4j2/pull/367#issuecomment-652152990 I've looked at the linked documentation and am fine with this in principle. I have not looked to see if leaving any of the fields uninitialized would cause problems, but I f

[GitHub] [logging-log4j2] vy commented on pull request #367: avoid initialize 'volatile' fields with default values

vy commented on pull request #367: URL: https://github.com/apache/logging-log4j2/pull/367#issuecomment-652000782 Hey @turbanoff! Thanks for the heads up and PR, appreciated! I will need some time to wrap my mind around the change set and approve it -- unless some other committer steps forw

[CI][FAILURE] log4j/release-2.x#69 has potential issues

There is a build failure in log4j/release-2.x. Build: https://builds.apache.org/job/log4j/job/release-2.x/69/ Logs: https://builds.apache.org/job/log4j/job/release-2.x/69/console Test results: https://builds.apache.org/job/log4j/job/release-2.x/69/testReport/ Changes: https://builds.apache.org/jo

[GitHub] [logging-log4j2] vy commented on pull request #362: LOG4J2-2749 - fix JSON Layout output containing empty values while configured otherwise

vy commented on pull request #362: URL: https://github.com/apache/logging-log4j2/pull/362#issuecomment-651978776 Hey @gagoman! We already have the Jackson version upgrade along with another change (#335) waiting for its last review by @rgoers. Nevertheless, your changes include a test, whi

[jira] [Work logged] (LOG4J2-2749) JsonLayout KeyValuePair should not log json key which has empty or blank value

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

[GitHub] [logging-log4j2] vy merged pull request #362: LOG4J2-2749 - fix JSON Layout output containing empty values while configured otherwise

vy merged pull request #362: URL: https://github.com/apache/logging-log4j2/pull/362 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

[jira] [Work logged] (LOG4J2-2749) JsonLayout KeyValuePair should not log json key which has empty or blank value

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

[jira] [Commented] (LOG4J2-2749) JsonLayout KeyValuePair should not log json key which has empty or blank value

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

[jira] [Created] (LOG4J2-2881) NullPointerException thrown on Hive startup

Renukaprasad C created LOG4J2-2881: -- Summary: NullPointerException thrown on Hive startup Key: LOG4J2-2881 URL: https://issues.apache.org/jira/browse/LOG4J2-2881 Project: Log4j 2 Issue Type: