The GitHub Actions job "CI - Groovy Joint Validation Build" on 
grails-core.git/fix/spring-dm-example-in-commit-bom has failed.
Run started by GitHub user jamesfredley (triggered by jamesfredley).

Head commit for run:
e08bb1e81534abd921a91940f08e222787a0c03d / James Fredley 
<[email protected]>
fix: manage the Spring DM example's versions from dependencies.gradle

The example imported org.apache.grails:grails-bom through
io.spring.dependency-management, which resolves BOM imports in its own
detached configuration. That configuration never sees the project
substitution in gradle/functional-test-config.gradle, so the import could
only ever be satisfied from a repository - which meant the example validated
whichever BOM was last published rather than the one in the commit, and
failed outright on a version that had never been published, taking CI down
on a newly created release branch before it could publish anything.

Serving the in-commit BOM from a local repository was tried and abandoned:
generating the poms early enough for Spring DM realizes the BOM projects
before gradle/cli-companion-bom-constraints.gradle has discovered
cliArtifactId, which silently drops every CLI companion constraint from the
generated and published BOM, and generating them late enough for a complete
BOM is already too late for the import to see them.

Drop the BOM artifact import instead and manage the example's versions from
dependencies.gradle, which is the single source of truth and which this
example already read for its logback and jackson overrides. The example
still sets bom = null and still applies io.spring.dependency-management, so
it continues to cover a migrated Grails 7 application whose versions are
managed by Spring DM rather than by the platform.

Spring Boot's own BOM is still imported automatically and silently supplied
older Groovy, commons-codec and log4j versions wherever an explicit entry
was missing, so its version properties are overridden from
dependencies.gradle as well. verifyDependencyManagementVersions asserts the
resolved versions on the compile and integration test runtime classpaths and
fails if any of them drift, since that divergence is invisible to a
successful build.

Assisted-by: claude-code:claude-opus-5

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

With regards,
GitHub Actions via GitBox

Reply via email to