[GitHub] [logging-log4j-kotlin] rocketraman merged pull request #13: Ensure OSGi compatibility

rocketraman merged pull request #13: URL: https://github.com/apache/logging-log4j-kotlin/pull/13 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

[GitHub] [logging-log4j2] wuqian0808hundsun commented on pull request #428: Avoid kafka thread leak - LOG4J2-2916

wuqian0808hundsun commented on pull request #428: URL: https://github.com/apache/logging-log4j2/pull/428#issuecomment-725793729 @vy Could u help to advise if there is anything else should I do before merging? This is an

[CI][SUCCESS] Logging/log4j/release-2.x#145 back to normal

BUILD SUCCESS Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/145/ Project: release-2.x Date of build: Wed, 11 Nov 2020 18:56:44 + Build duration: 1 hr 7 min and counting JUnit Tests Name:

[CI][UNSTABLE] Logging/log4j/release-2.x#144 has test failures

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/144/ Project: release-2.x Date of build: Wed, 11 Nov 2020 17:23:00 + Build duration: 1 hr 9 min and counting JUnit Tests Name:

[GitHub] [logging-log4j2] sandeepbarnwal edited a comment on pull request #436: LOG4J2-2850 Fix ctor used in LocalizedMessageFactory#newMessage().

sandeepbarnwal edited a comment on pull request #436: URL: https://github.com/apache/logging-log4j2/pull/436#issuecomment-725508202 > Thanks so much @sandeepbarnwal! Would you mind updating `/src/changes/changes.xml` and adding a simple test (to `LocalizedMessageTest`?) as well, please?

[GitHub] [logging-log4j2] sandeepbarnwal commented on pull request #436: LOG4J2-2850 Fix ctor used in LocalizedMessageFactory#newMessage().

sandeepbarnwal commented on pull request #436: URL: https://github.com/apache/logging-log4j2/pull/436#issuecomment-725508202 > Thanks so much @sandeepbarnwal! Would you mind updating `/src/changes/changes.xml` and adding a simple test (to `LocalizedMessageTest`?) as well, please?

[GitHub] [logging-log4j-kotlin] jvz commented on pull request #13: Ensure OSGi compatibility

jvz commented on pull request #13: URL: https://github.com/apache/logging-log4j-kotlin/pull/13#issuecomment-725460166 Nah, go ahead. There might be some OSGi bugs in Log4j itself, but those would be handled separately. On Wed, Nov 11, 2020 at 08:16 Raman Gupta wrote: >

[GitHub] [logging-log4j-kotlin] rocketraman commented on pull request #13: Ensure OSGi compatibility

rocketraman commented on pull request #13: URL: https://github.com/apache/logging-log4j-kotlin/pull/13#issuecomment-725447578 @jvz This PR LGTM. Are there any hoops we need to jump through before merging? This is an

[jira] [Created] (LOG4J2-2958) MD5 hash is deprecated

Sebb created LOG4J2-2958: Summary: MD5 hash is deprecated Key: LOG4J2-2958 URL: https://issues.apache.org/jira/browse/LOG4J2-2958 Project: Log4j 2 Issue Type: Bug Reporter: Sebb The

[jira] [Commented] (LOG4J2-2025) Support Tomcat JULI's per-webapp JUL logging by implementing java.util.logging.Handler

[ https://issues.apache.org/jira/browse/LOG4J2-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17229878#comment-17229878 ] Ilamparithi Natarajan commented on LOG4J2-2025: --- Thanks [~mattsicker]  I have opened

[GitHub] [logging-log4j2] ilam-natarajan opened a new pull request #437: LOG4J2-2025 jul-log4j bridgehandler

ilam-natarajan opened a new pull request #437: URL: https://github.com/apache/logging-log4j2/pull/437 backporting [LOG4J2-2025](https://issues.apache.org/jira/browse/LOG4J2-2025) from 3.x (master) to 2.x This change allows redirecting JUL from a webapp without impacting