+1
Git tag log4j-2.19.0-rc2 tested with
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/maven
Java version: 1.8.0_345, vendor: Temurin, runtime:
/usr/lib/jvm/temurin-8-jdk/jre
Default locale: de_DE, platform encoding: UTF-8
OS name:
+1
Tested against
* WildFly Core main with -DallTests ( https://github.com/wildfly/wildfly-core/ )
* JBoss Logging 3.4 branch (
https://github.com/jboss-logging/jboss-logging/tree/3.4 )
* Log4j2 JBoss Logmanager main(
https://github.com/jboss-logging/log4j2-jboss-logmanager )
Regards
Boris
> R
Hello Piotr,
> Piotr P. Karwasz hat am 29.08.2022 20:03 CEST
> geschrieben:
> The next release (2.19.0) will require updating our Log4j2 -> SLF4J
> and SLF4J -> Log4j2 bridges to SLF4J 2.0. If that is also a blocker
> for Wildfly we'll probably manage to release 2.19.0 before your next
> Wildfly
Hello,
I have a small HelloWorld to test the issue.
https://github.com/apache/logging-log4j2/pull/1008 works with it, the
privileges are obtained from the caller, both in a positive (caller is the
appserver) and a negative (caller is the app) way.
LOG4J2-3579 is as blocker to integrate 2.18.0
