This is an automated email from the ASF dual-hosted git repository. jamesfredley pushed a commit to branch 9.0.x in repository https://gitbox.apache.org/repos/asf/grails-core.git
commit 76ad6d4da9179a6c90ac560e95b02b65bcae36a1 Author: James Fredley <[email protected]> AuthorDate: Thu Jul 30 12:43:50 2026 -0400 build: exclude the Spring DM example until 9.0.0-SNAPSHOT is published Bumping projectVersion to 9.0.0-SNAPSHOT broke this branch's build. The Spring Dependency Management example imports org.apache.grails:grails-bom at the project version through io.spring.dependency-management, which resolves that import with its own detached configuration and so bypasses the local project substitution. No 9.0.0-SNAPSHOT BOM has ever been published, so the import resolved to nothing, every managed version came back empty, and the build failed with "Could not find <group>:<artifact>:" - which in turn kept CI from publishing the snapshot that would have fixed it. Set the bomSnapshotNotPublished flag added in 8.0.x so the example is left out of the build graph until the first 9.0.0-SNAPSHOT publish succeeds. Assisted-by: claude-code:claude-opus-5 --- gradle.properties | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/gradle.properties b/gradle.properties index 1f0c7441e9..4f46932883 100644 --- a/gradle.properties +++ b/gradle.properties @@ -20,6 +20,12 @@ javaVersion=21 githubBranch=9.0.x githubSlug=apache/grails-core +# 9.0.0-SNAPSHOT has never been published, so the Spring Dependency Management +# example cannot resolve its grails-bom import yet. Delete this line once the first +# 9.0.0-SNAPSHOT publish succeeds - the flag is presence-based, so setting it to +# false still excludes the example. See settings.gradle for the full explanation. +bomSnapshotNotPublished=true + # Note: BOM dependencies are defined in dependencies.gradle files to allow for dependabot updates # Project dependency versions not managed by BOMs
