From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Maybe make feature variants for the different Gradle versions?

hmm, there doesn't seem to be any public way to register `@Option`-equivalents at runtime (as is possible with simple properties via `task.getInputs().property(...)`)

so right, it looks like your options are either feature variants or registering different task subclasses based on Gradle version

That’d be also the cleanest way I guess. Thanks, folks!

IMG_7918.png

Don't you think this is a breaking change introduced in `8.2`?

I would even tend to say it is a bug.
I guess it goes through validation that it is a valid option, then removes the prefix, doesn't find the option to set and just ignores it.

If it would instead throw a "no such option" exception, it would be a breaking change.

But it should probably be able to set that option still instead and maybe even add `--header` automatically if there is `--no-header`.

Reported as: <https://github.com/gradle/gradle/issues/25658>

Thanks for catching this and reporting it.

The issue is fixed with `8.2.1`. Thanks, folks! :blue_heart: