This message was deleted.

sourceSets {
    openApi {
        java {
            srcDir(tasks.openApiGenerate.outputDir)
        }
    }
}

kind of looks like it works (would love to know why they don't create their own...)

main.extendsFrom(openApiCompile)

just means that all dependencies that are declared on

openApiCompile

or any it extends are also declared on

main

, but it does not imply any dependency from either to the other other than that.

Well that didn't work because the generator generates a repository route and not a source directory

Well that didn't work because the generator generates a repository route and not a source directory

Let me quote myself:

and the open api generation tasks can be configured to meet that criterion

I did this already in the past myself already, so I know it works if you bend it to your will

I have no plan on generating it in build anymore

I think I detailed here or on the forums already in the past how to properly bend the open api plugin to your will, you just need to find it. 🙂

Oh man why you got to make me do that. Realistically though one of the reasons we're doing this is because it's still using the JSR 305 jar and that needs to go away. So did you also describe on how to deal with that? Also in some cases the open API spec that we're getting is not as useful as we'd like so it is possible that being able to modify the code by hand is a better solution

Here it is: https://www.linen.dev/s/gradle-community/t/495979/i-use-the-org-openapi-generator-plugin-and-to-add-the-genera

I'll take a look tomorrow, thanks

Yeah, well, then maybe just use the build as-is. Or still do it like I describe but not in

main

sourceSet but a separate like you already half-way did and then depend from

main

to that

Yeah I tried to figure out how to make Main depend on it. No dice. I probably wouldn't use it completely as is because I'll probably throw away a lot of those root files. Like I said though at that point Gradle basically becomes just a place the store the task configuration. I wouldn't run it at build anymore. So it would only get run if we need to update from the spec.

You don't know to throw away those files, you can simply tell the plugin not to generate them, like I described in the link.

Yeah like I said I'll read it tomorrow. Keep in mind I did not write the initial implementation of using this plugin. I have never seen it before and it certainly doesn't seem to be documented to do what you're saying to do.... I do know that you can throw away certain files though. I'm not certain that solves all of our problems. Nothing solves the problem that the Open API spec doesn't generate all of the code that we want it to. At some point they decided that instead of creating real objects they were going to have us generate maps that stored a generic object that held something that was just object... So now we have to write our own class to serialize properly in order to actually have some type safety versus just having maps all the way down... We do not control the spec

In what way do you think

main

is special here? Can you show an example? It should not really be specials except that it is wired to some places.

can I safely get rid of the first 2 lines?

compileJava.dependsOn tasks.openApiGenerate
sourcesJar.dependsOn tasks.openApiGenerate

sourceSets {
    main {
        java {
            srcDir(tasks.openApiGenerate)
        }
    }
}

> can I safely get rid of the first 2 lines? > Yes, any explicit

dependsOn

that does not have a lifecycle task on the left-hand side is a code smell anyway. And by defining the generation task as source dir, any task needing sources gets the generated sources and automatically has the necessary task dependency, that's the point. :-) > unfortunately, this doesn't do the right thing... it's still generating the entire structure > Well, try to follow what I wrote in the conversation I linked you to. Your configuration is different from what I wrote.

Oh yeah because I didn't link the new code entirely

For example all the generate...false stuff and the ignore file.

hmm... ok, I'll work on it more later, somehow I missed that, and/or had tried some of that in a previous incarnation