Skip to content
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

Use configuration avoidance API, per Gradle guidelines #642

Open
Smoofie opened this issue May 20, 2022 · 0 comments
Open

Use configuration avoidance API, per Gradle guidelines #642

Smoofie opened this issue May 20, 2022 · 0 comments

Comments

@Smoofie
Copy link

Smoofie commented May 20, 2022

printVersion task should be registered using Gradle configuration avoidance API, there is no reason to eagerly create and configure it.

Gradle docs: https://docs.gradle.org/current/userguide/task_configuration_avoidance.html#sec:how_do_i_defer_creation

Effective task configuration avoidance requires build authors to change instances of TaskContainer.create(java.lang.String) to TaskContainer.register(java.lang.String).

Any chance that it could be migrated?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant