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

Gradle Community

does it _have_ to depend on the language-specific compile task(s)?  Perhaps depending on lifecycle tasks (e.g `assemble`) is cleaner

`dependsOn(classes)`, but ideally you'd rather use the source set's output as input to the task

`assemble` is too late — it’s an instrumentation task I’m talking about.

<@UDC9Q9RD0> I am actually relying on `sourceSet`’s output currently having the `dependsOn(sourceSet.classesTaskName)`.
Seems like something’s still wrong on my side — the instrumentation task is run too early and classes aren’t written yet:

```...
&gt; Task :plugin:core:classes
&gt; Task :plugin:core:setupInstrumentCode

&gt; Task :plugin:core:instrumentCode FAILED
[ant:instrumentIdeaExtensions] /Users/hsz/Projects/3rd/Perl5-IDEA/plugin/core/src/main/java/com/perl5/lang/perl/idea/configuration/settings/sdk/Perl5SdkPanel.form: Class to bind does not exist: com.perl5.lang.perl.idea.configuration.settings.sdk.Perl5SdkPanel```
But the second run works fine as the `plugin:core:classes` task is already `UP-TO-DATE`:
```...
&gt; Task :plugin:core:classes UP-TO-DATE
&gt; Task :plugin:core:setupInstrumentCode
&gt; Task :plugin:core:instrumentCode
&gt; Task :plugin:core:classpathIndexCleanup

BUILD SUCCESSFUL in 1s```

Note that by "use the source set's output" I rather meant something like `classesToProcess.from(fileTree(sourceSet.output.classesDirs))` and not using `dependsOn` at all.
But using `dependsOn(source.SetclassesTaskName)` should work too. I would print the inputs and whether they exist or not at the start of the task (possibly in a `doFirst`) to try to debug this.

Ok, all classes were available for the task, but then ant taks was spin up and missed them. Anyways, thanks to your latest comment I went into the proper direction. Thanks! :slightly_smiling_face: