This is an automated email from the ASF dual-hosted git repository.

gnodet pushed a commit to branch stacked/build-report
in repository https://gitbox.apache.org/repos/asf/maven.git

commit d09af07f28c4191db71798f4f805b875bc47fe2d
Author: Guillaume Nodet <[email protected]>
AuthorDate: Mon Oct 26 09:40:00 2026 +0000

    fix: correct Javadoc on printStackTrace bridge — remove unimplementable 
advice
---
 .../main/java/org/apache/maven/logging/slf4j/MavenSimpleLogger.java  | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git 
a/impl/maven-logging-slf4j/src/main/java/org/apache/maven/logging/slf4j/MavenSimpleLogger.java
 
b/impl/maven-logging-slf4j/src/main/java/org/apache/maven/logging/slf4j/MavenSimpleLogger.java
index 8c7022d083..17a9c8e25e 100644
--- 
a/impl/maven-logging-slf4j/src/main/java/org/apache/maven/logging/slf4j/MavenSimpleLogger.java
+++ 
b/impl/maven-logging-slf4j/src/main/java/org/apache/maven/logging/slf4j/MavenSimpleLogger.java
@@ -102,8 +102,9 @@ protected void writeThrowable(Throwable t, Consumer<String> 
stream) {
      * This method always resets the depth counter to 0. Subclasses must not 
call
      * {@code super.printStackTrace(t, stream, prefix)} mid-chain (e.g. from 
within
      * their own cause/suppressed traversal), as doing so would defeat the
-     * {@code MAX_THROWABLE_DEPTH} guard on deeply chained exceptions. 
Override the
-     * private 4-arg variant instead if mid-chain calls are needed.
+     * {@code MAX_THROWABLE_DEPTH} guard on deeply chained exceptions.
+     * Subclasses that need mid-chain cause traversal should implement their 
own
+     * depth-tracking logic rather than calling this bridge re-entrantly.
      */
     protected void printStackTrace(Throwable t, Consumer<String> stream, 
String prefix) {
         printStackTrace(t, stream, prefix, 0);

Reply via email to