borinquenkid opened a new issue, #16635: URL: https://github.com/apache/grails-core/issues/16635
`META-INF/spring.schemas` maps `http://grails.org/schema/context/grails-context.xsd` to `org/grails/spring/context/annotation/grails-context.xsd`, but that file lives under `grails-core/src/main/groovy`, which the build does not treat as a resource directory. The XSD is therefore missing from the published `grails-core` jar (checked `grails-core-8.1.0-SNAPSHOT.jar`: only `spring.schemas` is there). An XSD-validating parse of `<grails:component-scan>` cannot resolve its schema locally and Xerces falls back to fetching `http://grails.org/schema/context/grails-context.xsd` over the network. The same is true on `8.0.x` and `9.0.x`, so this is not caused by the Java-to-Groovy conversion. Packaging the XSD, for example with ```groovy processResources { from('src/main/groovy') { include '**/*.xsd' } } ``` fixes it. Specs that parse `<grails:component-scan>` could then turn schema validation back on. Found in review of #16586. -- 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]
