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

Gradle Community

Most probably not.
But if you properly registered the code generation task using something like `srcDir(openApiGenerateTask)` instead of hard-wiring directory paths, you should already have the necessary dependency automatically.

```sourceSets {
    main {
        java {
            //            srcDir(tasks.named('openApiGenerate'))
            // need to add subfolder instead of root of the task output

            srcDir(tasks.openApiGenerate.getOutputDir().get() + "/src/main/java")
        }
    }
}```
is, insufficient? what else should I be looking at?

<https://github.com/diffplug/spotless/tree/main/plugin-gradle#java>

Yes, that's insufficient, as you do *not* configure the task, but a semi-hard-coded path.

`srcDir(tasks.openApiGenerate)` if it declares the outputs properly.

If you need that mapping, do

`srcDir(tasks.openApiGenerate.map { it.getOutputDir().get() + "/src/main/java" })` or something like that.

This way the task provider still carries over the necessary task dependency.

yeah, it doesn't output that subdir correctly

Well, depends on how you configure it, I use the plugin myself, but it needs a bit of fiddling to get it right, yep

*sigh* I thought I had `getOutputDir()` right... guess not... I'm not going to play guessing games or source dive for this. Other dev can do it if it's that important to him not to use `dependsOn`. Based on the API for spotless I'm not even sure it would work anyways

```&gt; Could not find method getOutputDir() for arguments [] on provider(task 'openApiGenerate', class org.openapitools.generator.gradle.plugin.tasks.GenerateTask) of type org.gradle.api.internal.tasks.DefaultTaskCollection$ExistingTaskProvider_```


I probably said it before, but I cannot resist. :slightly_smiling_face:
If you switch to Kotlin DSL, all the guessing game wents away. :slightly_smiling_face:

and I said you were preaching to the choire :wink:

I'm sure you understand the "I've already been told no"

Poor you.
Sorry I cannot remember that, too many people I talk to here :slightly_smiling_face:

although my response to spending further time on this is, you said 80/20, I'm not spending more time on this. I think that may be followed with, if you want me to I'm switching to kotlin to reduce that time

you know what's funny? I think when I wrote my own buildSrc version I didn't have this problem...

it tried to format the generated sources, and then I told it no, and I think it worked. This didn't happen

If you want to figure out the proper setup, how just going the "bad" way and defining the dependency or at least the must-run-after manually as suggested by the error?

this was my setup

```tasks.named("spotlessJava") {
    dependsOn(tasks.named("openApiGenerate"))
}```


least correct solution to the problem :stuck_out_tongue:

just doesn't seem like a problem worth spending hours on