The GitHub Actions job "CI - Groovy Joint Validation Build" on grails-core.git/8.0.x has succeeded. Run started by GitHub user jamesfredley (triggered by jamesfredley).
Head commit for run: 57883c41e4519b5e5cdbc6e6a9ef4a67a2c98f0f / James Fredley <[email protected]> build: allow excluding the Spring DM example on an unpublished branch version The Spring Dependency Management example imports grails-bom as a Maven BOM through io.spring.dependency-management, which resolves the import with its own detached configuration and so bypasses the local-project substitution in gradle/functional-test-config.gradle. settings.gradle already documented that this only works when org.apache.grails:grails-bom:<projectVersion> is already published, and already excluded the example during a reproducible release build for exactly that reason. A newly created release branch is the same condition. As soon as projectVersion is bumped to a version that has never been published, the BOM import resolves to nothing, every managed version comes back empty, and the build fails with "Could not find <group>:<artifact>:" - before CI can publish the snapshot that would fix it. Extend the existing guard with a presence-based -PbomSnapshotNotPublished so such a branch can exclude the example until its first snapshot publish succeeds. The default build graph is unchanged. Assisted-by: claude-code:claude-opus-5 Report URL: https://github.com/apache/grails-core/actions/runs/30557394023 With regards, GitHub Actions via GitBox
