For the record, I've created this issue regarding the basedir, which currently doesn't seem to work correctly in the jOOQ-codegen-gradle plugin: https://github.com/jOOQ/jOOQ/issues/16133
On Tuesday, January 16, 2024 at 6:17:13 PM UTC+1 Lukas Eder wrote: > On Tue, Jan 16, 2024 at 5:53 PM Kevin Jones <[email protected]> > wrote: > >> Thanks Lukas, >> >> I read the discussion about the plugin's dependencies and I think what >> you've done is correct, adding it to the docs would be good :) >> >> As to the sourceset, there are two things happening independently that I >> feel should be dependent: code is generated to a location and the sourceset >> is created. >> >> In my case I want my code to be generated to 'build/generated/src/java' >> and I want this to be my sourceset. >> >> Now, I can configure the plugin to put the generated code in >> 'build/generated/src/java' by setting the basedir and the target.directory >> properties. However it's not setting this to be the sourceset, it uses some >> default value. If I want a non-default directory to be the sourceset then >> I have to do that myself in the Gradle file (which I was doing previously) >> >> It seems that at the moment you create the sourceset location >> independently of the output location of the code generation. You always >> create the sourceSet at ',/generated/java', you seem to ignore the basedir >> property. Maybe it could be changed so that the sourceset location is the >> same as the location of the generated source? >> I haven't used multiple executions so I'm don't know your sourceset >> creation plays into that, >> > > Well, I fixed 2 bugs just today (keeping in mind that this is a very new > feature): > > - https://github.com/jOOQ/jOOQ/issues/16083 > - https://github.com/jOOQ/jOOQ/issues/16084 > > So there might be more bugs. I'll double check on the basedir feedback > tomorrow. > > Note, you can always just use ${projectDir} in your directory definition: > > directory = "${projectDir}/generated/java" > > That's probably easier anyway. > > (BTW, the docs show an 'executions' element but I can't see that in the >> XSD, not sure if it should be in there) >> > > The XSD starts at configuration. The name "executions" was simply chosen > because I'm a Maven guy, and Maven plugins have executions, and I found > this too useful a feature of plugins to just not have in gradle as well (I > was surprised this doesn't come out of the box in gradle, but I'm still > discovering the idiomatic way to use gradle). But it's a feature of the > plugin, not of the code generator, which doesn't have a concept of > executions (or build system, etc.), so indeed, it shouldn't be in the XSD. > I'm not sure how to convey this in the docs. This stuff is all very > standardised in Maven, so no additional docs are needed, but in "wild west > gradle," I guess every plugin invents their own wheels and needs to come up > with intuitive documentation... > > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/2a09268f-d0cb-41f8-acdd-b9749f617f82n%40googlegroups.com.
