vy commented on issue #2794: URL: https://github.com/apache/logging-log4j2/issues/2794#issuecomment-2267564572
@linghengqian, your Status Logger setup is broken by a combination of Status Logger enhancements introduced in Log4j `2.23.1` and `<log4j.debug>true` line in `/pom.xml` of the Hive repository, which gets injected into the `systemPropertyVariables` configuration of `maven-surefire-plugin`. You can view the effective POM using: ``` mvn help:effective-pom -pl hplsql -Doutput=pom-effective.xml ``` Remove `<log4j.debug>true</log4j.debug>` line in `/pom.xml` and following passes: ``` mvn install -N # Install `pom.xml` changes mvn test -pl hplsql -Dtest=TestHplsqlLocal#testConversion ``` Details of how Status Logger works and the effect of `log4j.debug` on it can be found in [the Status Logger manual](https://logging.staged.apache.org/log4j/2.x/manual/status-logger.html#debug). Status Logger is intended for troubleshooting Log4j itself and its components. I strongly advise you to avoid configuring it unless you are troubleshooting a Log4j issue. -- 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 the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
