You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
Lots of warnings when run with Gradle 6.x releases. Here are some examples
Any properties and getters on tasks that are not inputs or outputs whould be annotated
@Internal
to avoid this warning.The text was updated successfully, but these errors were encountered: