You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@grails.apache.org by GitBox <gi...@apache.org> on 2026/10/03 21:54:49 UTC

[GH] (grails-core/fix/mongodb-boot-autoconfiguration-registration-8.0.x): Workflow run "Groovy Snapshot Canary Build" is working again!

The GitHub Actions job "Groovy Snapshot Canary Build" on grails-core.git/fix/mongodb-boot-autoconfiguration-registration-8.0.x has succeeded.
Run started by GitHub user codeconsole (triggered by codeconsole).

Head commit for run:
28956fc2674b4aae8e527d1825b0fed82c4dd7a2 / Scott Murphy Heiberg <sc...@alwaysvip.com>
Register the GORM for MongoDB Spring Boot auto-configuration where Boot reads it

The imports file naming MongoDbGormAutoConfiguration was under
META-INF/services/spring/, which Spring Boot does not read; it reads
META-INF/spring/. So a Spring Boot application with
grails-data-mongodb-spring-boot on its classpath got no MongoDatastore
and no GORM data services. The module's own example application failed
to start, because BookController's BookService was never registered.
Nothing noticed: the tests import the auto-configuration explicitly, and
the example's test builds a MongoDatastore by hand rather than starting
the application.

The file is now under META-INF/spring/, as in every other module, and a
test starts a Spring Boot application that imports nothing and uses GORM.

Report URL: https://github.com/apache/grails-core/actions/runs/37151322267

With regards,
GitHub Actions via GitBox