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/08/31 22:49:11 UTC

[GH] (grails-core/feat/beans-dsl-qualified-autoconfiguration-name-8.0.x): Workflow run "CI" is working again!

The GitHub Actions job "CI" on grails-core.git/feat/beans-dsl-qualified-autoconfiguration-name-8.0.x has succeeded.
Run started by GitHub user codeconsole (triggered by codeconsole).

Head commit for run:
cfb1b1e10ebc5cc61612de99c2246e048350a87c / Scott Murphy Heiberg <sc...@alwaysvip.com>
Cover the qualified sibling end to end, not just at the AST level

The spec in grails-beans-dsl proves the sibling is generated under the qualified
name, but the point of accepting one is that an excludeName, a before=/after= or
a test import still resolves it - and that runs through the class file landing in
the named package, the build's AutoConfiguration.imports scan recording it there,
and Spring Boot discovering it. None of that was exercised.

SalutationGrailsPlugin names a sibling in beandsl.example.plugin.web while
Salutation itself stays in the descriptor's package, so the bean(...) referencing
it unqualified also covers type resolution surviving the move.

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

With regards,
GitHub Actions via GitBox