jamesfredley opened a new pull request, #15824:
URL: https://github.com/apache/grails-core/pull/15824

   Fixes #14915
   
   ## Summary
   
   - Lazily initialize BeanBuilder XML support so ordinary `resources.groovy` 
DSL evaluation does not create Spring XML reader/context infrastructure.
   - Preserve XML compatibility for `importBeans` with XML resources and Spring 
XML namespace DSL support through `xmlns`.
   - Enable `grails-spring` module test configuration and add regressions for 
plain DSL, XML import, and namespace support.
   - Document the Grails 8 compatibility behavior in the upgrade notes and 
Spring DSL guide.
   
   ## Verification
   
   - `JAVA_HOME=/home/james/.jdks/corretto-21 
PATH=/home/james/.jdks/corretto-21/bin:$PATH ./gradlew :grails-spring:test 
--rerun-tasks`
   - `JAVA_HOME=/home/james/.jdks/corretto-21 
PATH=/home/james/.jdks/corretto-21/bin:$PATH ./gradlew :grails-spring:codeStyle`
   - External BeanBuilder driver against built `grails-spring` runtime 
classpath: `PASS plain BeanBuilder DSL did not initialize XML support`
   - Review gate: Oracle and Codex reviewed staged hash 
`f1e6f82bdd5a4035a8230306b3d519b03ac1a61a` as GREEN. Codex only flagged 
regenerated untracked `.omo/run-continuation` session metadata, which was not 
staged or committed.
   
   ## Full-suite notes
   
   - `./gradlew clean` completed successfully.
   - `./gradlew aggregateViolations --continue` was attempted and failed on 
unrelated existing compile errors:
     - 
`grails-validation/src/main/groovy/grails/validation/Validateable.groovy`: 
unable to resolve `groovy.transform.Virtual`
     - `grails-data-graphql/core/.../Arguable.groovy` and 
`ComplexTyped.groovy`: static type checking cannot find `withDelegate(Closure, 
Object)`
   - `./gradlew :grails-test-report:check --continue` was attempted and 
exceeded the 20 minute tool timeout after running broad test output.
   


-- 
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]

Reply via email to