Branch: refs/heads/proposal-console-warn-rendering Home: https://github.com/xwiki/xwiki-commons Commit: bbe6fd9b143ace4b20c2eeb82bc582549e8f4520 https://github.com/xwiki/xwiki-commons/commit/bbe6fd9b143ace4b20c2eeb82bc582... Author: Vincent Massol <[email protected]> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M xwiki-commons-core/xwiki-commons-logging/xwiki-commons-logging-api/src/main/java/org/xwiki/logging/Logger.java M xwiki-commons-core/xwiki-commons-logging/xwiki-commons-logging-logback/src/main/java/org/xwiki/logging/logback/internal/LogbackEventGenerator.java M xwiki-commons-core/xwiki-commons-logging/xwiki-commons-logging-logback/src/main/java/org/xwiki/logging/logback/internal/XWikiThrowableConverter.java M xwiki-commons-core/xwiki-commons-logging/xwiki-commons-logging-logback/src/test/java/org/xwiki/logging/logback/internal/XWikiThrowableConverterTest.java Log Message: ----------- [Misc] Let a log call force the full stack trace of a warning Some warnings exist only to record where they were called from, their exception carrying no information of its own, so shortening them to their root cause deletes their whole point. Such a call can now carry the xwiki.stacktrace marker to keep its full stack trace whatever the console is configured to shorten. Loggers can also be exempted by name, through a conversion word option or a Logback property, so that keeping the current rendering for a subset of the code does not require declaring a second appender: a pattern belongs to one encoder and one appender, and several file appenders writing to the same file need prudent mode. Reading the markers of the event through getMarkerList() rather than the deprecated getMarker() also stops the log event from losing all but its first marker on its way to the wiki UI. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-commons/settings/notifications