Good morning, folks! I wonder, what’s the profit of making a task inheriting

VerificationTask

? Does that interface provide a unified setter/getter, or is there any logic within Gradle internals?

Well, it has a property for ignoring failures. And it will be matched if someone does

tasks.withType<VerificationTask>().configureEach { ... }

or similar, but at least in the Gradle sources I see no such configuration. I don't think there is any additional implication.

Fwiw, you can't use

tasks.withType<VerificationTask>()

because

VerificationTask

isn't itself a

Task

(it would probably work with the Groovy DSL and thanks to type erasure)

Oh, right, for whatever reason

VerificationTask

does not extend

Task

. 😞

The reason I ask is that, for the sake of consistency, I have the

ignoreWarnings

lazy property introduced explicitly in my task.

@get:Input
abstract val ignoreWarnings: Property<Boolean>

Now, after I started using Managed Types, I run into conflicts – setter and getter are created for

Property<Boolean>

, but methods from that interface are raw

Boolean

. It was manageable previously, but now too much magic is involved and the easiest solution is to drop

VerificationTask

completely as syntax for end-user will not change (ok, for Kotlin DSL will, but that’s acceptable).

I'd guess it should be fine to remove it and optionally readd it after it was propertified 🙂

Thanks!