build(metadata): cleanup project.properties usage#559
Draft
MattSturgeon wants to merge 2 commits into
Draft
Conversation
…nships` Drop deprecated usage of `project.properties`. Replace manual key-segment marshaling with stonecutter's `to<type>()`. Improve error handling for invalid relationship fields.
…deps`, `reqs` maps Drop deprecated usage of `project.properties`. Replace manual key-segment marshaling with stonecutter's `to<type>()`.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
project.propertiesis deprecated since Gradle 9.6, for removal in Gradle 10.Migrate to
sc.propertiesand take advantage ofSCElement.to<type>()for simplifying deserialization.This approach is blocked by stonecutter#56, because
rawOrNulldoes not include "less specific" properties in theSCElementresult:For these properties: