-
Notifications
You must be signed in to change notification settings - Fork 66
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
Move to latest Gradle API and best practices #323
Comments
@int128 ping? |
bump on this? @int128 @jjohannes interested. especially wiht gradle 8.0 and whatever potentials are to be had by that |
I am still interested in contributing this. |
I am interested in contributing |
I have started some work in #409 to make the plugin configuration cache compatible, which is the minimum we need to continue using it. I would use that as the base to resolve this issue. It already moves a few things to "current best practices". |
This is not a request but a proposal. @int128 if you would like to see this done, I will provide a PR with the changes. But since this is a larger change, I want to ask first.
Describe the feature
We are using this plugin in a project with Kotlin DSL and noticed that the plugin lacks behind in some of the latest Gradle features we would like to consistently use in our project:
DirectoryProvider
instead ofFile
)TaskProvider<MyTask>
instead ofMyTask
in API/DSL for task configuration avoidance@CompileStatic
for Groovy code to be more performant at configuration times.Why do you want the feature?
We would like to consistently use the features listed above in out build together with this plugin.
Notes:
File
toDirectoryProperty
, you can still assign aFile
. You just also can assign lazy typed values -Provider<Directory>
- as well.Let me know if there are any concerns. If you would like to see this contributed, I would give it a try in a few days.
The text was updated successfully, but these errors were encountered: