efegokdemir commented on PR #2157: URL: https://github.com/apache/maven-resolver/pull/2157#issuecomment-5794163227
Addressed the review by keeping the original stdout/stderr diagnostics for the forked server process, whose isolated classpath has no SLF4J provider, while retaining SLF4J logging for in-process (`NO_FORK`) execution. Validation on JDK 21: - `mvn -pl maven-resolver-named-locks-ipc -am -DskipITs -DskipTests=false test` — PASS (13 tests) - `mvn -pl maven-resolver-named-locks-ipc -am -Prun-its verify` — FAIL in the existing IPC integration setup with `ByteChannelWrapper`/forked-server classpath errors; no assertion failure points to this logging-only change. - `git diff --check` — PASS The follow-up is commit `278d3be9c8e77467cc5edaabdc9910f0a7a2bea2`. -- 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]
