#15258 - fix - restore bom properties #15260
Merged
+2
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
This fixes the root issue of the properties not being generated due to the parallel resolution order of Gradle. Once the publish change is merged, we can merge this , and then re-evaluate the issue after both projects are published to maven for testing. |
codeconsole
approved these changes
Nov 26, 2025
jdaugherty
changed the title
jdaugherty
changed the title
matrei
approved these changes
Nov 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will fail until apache/grails-gradle-publish#16 is merged. Properties in the bom were broken because of not doing a deferred lookup of the pomCustomization closure. This change adopts the provider syntax for pomCustomization so that the property isn't looked up until execution