The GitHub Actions job "CI" on grails-core.git/fix/forge-logback-withjansi-devtools has failed. Run started by GitHub user jamesfredley (triggered by jamesfredley).
Head commit for run: a392fc918c5ef747a957a1eca26e8ba3cdb0c73e / James Fredley <[email protected]> Document why Jansi is disabled and why bootRun ANSI config is unconditional Address review feedback on the generated logback-spring.xml and the GrailsGradlePlugin bootRun configuration: - Add an explanatory comment in the generated logback-spring.xml noting that Jansi is intentionally disabled because it replaces System.out globally, which is incompatible with reloading tools (Spring Boot DevTools) and breaks console logging after a restart. Colors come from Spring Boot's %clr converter via CONSOLE_LOG_PATTERN and do not need Jansi. - Add a comment in GrailsGradlePlugin explaining that spring.output.ansi.console-available=true is set on every OS on purpose: it is not a force-on. Spring Boot's AnsiOutput DETECT mode still gates Windows out internally (return !OS_NAME.contains("win")), so legacy Windows consoles never receive raw ANSI escapes while macOS/Linux and modern terminals get colored bootRun output. These are comment-only changes; no behavior is modified. Assisted-by: claude-code:claude-4.8-opus Report URL: https://github.com/apache/grails-core/actions/runs/28454874253 With regards, GitHub Actions via GitBox
