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

Gradle 6.x warnings #187

Open
ysb33r opened this issue Jan 22, 2020 · 2 comments
Open

Gradle 6.x warnings #187

ysb33r opened this issue Jan 22, 2020 · 2 comments

Comments

@ysb33r
Copy link

ysb33r commented Jan 22, 2020

Lots of warnings when run with Gradle 6.x releases. Here are some examples

Property 'acl' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'bucketName' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'metadataProvider' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'prefix' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'source' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'storageClass' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'threads' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'delete' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.

Any properties and getters on tasks that are not inputs or outputs whould be annotated @Internal to avoid this warning.

@nedtwigg
Copy link

Just FYI, gradle 6.3 was just released. I believe the gradle schedule is 6.4, 6.5, then 7.0. So it's probably just a few months until this becomes a bit more urgent.

@abhinayagarwal
Copy link

Gradle 7.0 is already out and latest version of the plugin doesn't work because of aforementioned issues.

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

3 participants