-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Remove project from task extension #6038
Conversation
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.
I don't know much about Gradle plugins, but looks good to me.
cc. @manusa
@Sineaggi : Could you please fix style errors with |
dd353f7
to
cbade85
Compare
@Sineaggi : Do you know if this configuration cache requirement was added since Gradle 8.x ? |
I think since a minor version of Gradle 6.x, not sure which exactly. This does not prevent the plugin from running on Gradle 8.x, but it does break projects that attempt to enable configuration cache. |
Without these changes, we get the following error
No errors with this change. |
cbade85
to
a78c2cd
Compare
Normally I'd be able to create a test (via GradleRunner) that starts up Gradle with the plugin, but I wasn't having much luck getting that to work from maven. |
Quality Gate passedIssues Measures |
Good to merge? |
Yes it is. However, I'd like to check a few things locally. I'll probably merge on Friday. Sorry for the delay. |
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.
LGTM, thx!
Signed-off-by: Marc Nuri <marc@marcnuri.com>
In order to support Gradle's configuration cache, having the Project object in extensions/tasks is not allowed https://docs.gradle.org/current/userguide/configuration_cache.html#config_cache:requirements:disallowed_types. We can avoid that by injecting the ProjectLayout object directly which is legal.
Specifically