here s a good issue for the Gradle expert

Question

< danny> here s a good issue for the Gradle expert

danny · Answer

If that s a published artifact it should be an implicit dependency of the publication task

danny · Answer

That said I don t see anything there that would make your tests run either

danny · Answer

Let me look at the release tasks more closely

danny · Answer

`clean build final` is probably all you need I think the readme on Spring release is wrong

robfletcher · Answer

I thought this line should establish the dependency <https github com robfletcher strikt blob master gradle published gradle L24>

robfletcher · Answer

`clean build final` is all I m doing

robfletcher · Answer

robfletcher · Answer

actually not even `clean`

danny · Answer

Weird the publication should be taking care of that

danny · Answer

You could wire an explicit dependsOn to assemble for dokkaJar

robfletcher · Answer

right I guess it s because I m hijacking the javadoc task with dokka

danny · Answer

`mustRunAfter` also doesn t cause tasks to run incidentally

danny · Answer

If the tasks aren t included in the task graph by the requested tasks they don t run

danny · Answer

That s what `dependsOn` is for

robfletcher · Answer

right all that s doing is making sure Javadoc doesn t overwrite the stuff Dokka generates The reason dokka runs is that dependency in the publication

robfletcher · Answer

might be a better way of turning off javadoc

danny · Answer

If I want to hijack a task have your new task depend on the old and set `enabled = false` on the original task

danny · Answer

Disabling the task doesn t affect the task graph and the dependency will still execute

robfletcher · Answer

aha

danny · Answer

In this case ```javadoc dependsOn dokka javadoc enabled = false```

danny · Answer

And `dokkaJar dependsOn dokka`

danny · Answer

Then when `dokkaJar` is called for the publication everything should happen implicitly

robfletcher · Answer

isn t that implied by dokkaJar having `from dokka `

danny · Answer

Yep any source that s buildable becomes an implicit dependency

robfletcher · Answer

so adding this ```javadoc dependsOn dokka javadoc enabled = false javadocJar dependsOn dokkaJar javadocJar enabled = false ```

robfletcher · Answer

Hmm ```Invalid publication nebula multiple artifacts with the identical extension and classifier jar javadoc ```

robfletcher · Answer

That ll be my dokkaJar conflicting with the javadoc one applied by nebula release

robfletcher · Answer

Ok I have another way ```javadoc enabled = false task javadocJar type Jar overwrite true group = documentation description = Assembles Kotlin docs with Dokka classifier = javadoc from dokka ``` Then I can remove the publication stuff and Nebula just does it for me because I hijacked the regular javadocJar task

robfletcher · Answer

well that fixed the problem