The GitHub Actions job "CI" on grails-core.git/fix/dispatcher-servlet-autoconfig-backoff has succeeded. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: c87af0fddeb5c33490e35cd3c3db2c23f6c55a1c / Scott Murphy Heiberg <[email protected]> Back off Spring Boot's DispatcherServlet auto-configuration ControllersAutoConfiguration defines its own `dispatcherServlet` (a GrailsDispatcherServlet) and `dispatcherServletRegistration` beans, but it was not ordered before Spring Boot's DispatcherServletAutoConfiguration. Spring Boot therefore registered its own beans first and Grails overrode them, producing two INFO "Overriding bean definition for bean 'dispatcherServlet'/'dispatcherServletRegistration'" messages on startup and relying on bean-definition overriding to win. Add DispatcherServletAutoConfiguration to the auto-configuration `before` list so Grails registers these beans first. Spring Boot's DefaultDispatcherServletCondition and DispatcherServletRegistrationCondition then see the existing beans and back off via their own conditions instead of being overridden. Runtime behavior is unchanged - GrailsDispatcherServlet still handles requests - but the override and its log noise are eliminated. Report URL: https://github.com/apache/grails-core/actions/runs/28267293005 With regards, GitHub Actions via GitBox
