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

Gradle Community

If default behaviour is expressed in tasks you could try to disable default tasks when user configures the extension

I guess that'd work. But they'd still show up in `./gradlew --tasks` etc, right?

Not sure if it would be enough in your case though

If they still show in `tasks` output you could also try to reset default tasks group

yea but then they'll still show in `./gradlew --tasks --all` or `./gradlew build -m` and stuff like this

Not the end of the world. Just adding some noise for someone that's not hyper familiar with the setup this might create questions

Maybe I should just mandate users to configure something

At least with `enabled = false` they aren't cluttering `./gradlew tasks` output. But they still are visible in `./gradle tasks --all`. Not sure about dry run