This message was deleted.

Using

afterEvaluate

is practically always wrong. It is in 98.7 % of the cases just a symptom treatment, shifting problems to later times and makes them harder to reproduce, debug, and fix, and mainly introduces timing problems and race conditions. Also on "how to configure it", I strongly suggest using Kotlin DSL instead of Groovy DSL. With Kotlin DSL you immediately get type-safe build scripts, much better and actually helpful error messages if you mess up the syntax, and amazingly better IDE support if you use a proper IDE like IntelliJ or AS. If the task is not readily available (

tasks.named("javaDocReleaseGeneration")

saying the task does not exist), the proper way is

tasks.withType(JavaDoc).matching { it.name == 'javaDocReleaseGeneration' }.configureEach { ... }

and in the docs of

JavaDoc

and in the Gradle userguide you can find how to configure the task, like for example

excludes.add('...').

Thank you for your answer. I see that the

javaDocReleaseGeneration

task is not listed on the Gradle Tasks output. with

tasks.withType(JavaDoc)

I don't get a match unfortunately

If it is not listed in

gw tasks --all

then are you sure that is its name?

Oh yes it is listed with

task --all

but it's a 'dynamic' task built by the variant 'release'. So it's there but i can not reference to it with

tasks.named("javaDocReleaseGeneration"){
    println it
}

Also not with

matching

? o_O

There is no 'JavaDoc' type task. Maybe it's from another type

gw help --task javaDocReleaseGeneration

shows you the type

Type JavaDocGenerationTask (com.android.build.gradle.tasks.JavaDocGenerationTask)

Well, then go on 🙂

Ok,

tasks.matching { it.name == 'javaDocReleaseGeneration' }.configureEach {
    println it.dokkaPlugins
}

It seems it's not a Javadoc Task but some kind of com.android.build.gradle.tasks.JavaDocGenerationTask i'm trying to find documentation for