-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle - Resolve platform properties when possible #45681
Conversation
We were always passing a <<ignored>> value for the native builder which is a problem. We now correctly get the values from the platform properties when possible.
@@ -117,7 +117,8 @@ protected Manifest manifest() { | |||
return baseConfig().manifest(); | |||
} | |||
|
|||
protected EffectiveConfig buildEffectiveConfiguration(ResolvedDependency appArtifact) { | |||
protected EffectiveConfig buildEffectiveConfiguration(ResolvedDependency appArtifact, | |||
Map<String, String> platformProperties) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A minor comment, it looks like you could pass an ApplicationModel
here now? Every invocation seems to be obtaining the two arguments from it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I tried to reduce my changes to the minimum. I pushed an additional commit.
Status for workflow
|
We were always passing a
<<ignored>>
value for the native builder which is a problem.We now correctly get the values from the platform properties when possible.
This is a follow-up for #45637 .