3.19.10 Release Breaks My Build

2024-06-19 Thread Kevin Jones
Hi Lucas, I'm using Gradle, which I know you love! I've just tried to update my build to 3.19.10, literally by changing the JOOQ version number from 3.19.9 to 3.19.10 and the build breaks. This is a Compose-Desktop app which is using the Kotlin Multiplatform plugin, that uses a couple of sourc

Re: 3.19.10 Release Breaks My Build

2024-06-19 Thread Lukas Eder
Hi Kevin May I tempt you to kindly provide a reproducer Lukas On Wednesday, June 19, 2024, Kevin Jones wrote: > Hi Lucas, > > I'm using Gradle, which I know you love! > > I've just tried to update my build to 3.19.10, literally by changing the > JOOQ version number from 3.19.9 to 3.19.10 and t

Re: 3.19.10 Release Breaks My Build

2024-06-19 Thread Lukas Eder
OK, I get it now. Before 3.19.10, we just didn't register any source sets at all, if there was no main source set. I'm assuming, you manually added the output directory to a source set in your case? On Wed, Jun 19, 2024 at 5:06 PM Lukas Eder wrote: > Hi Kevin > > May I tempt you to kindly prov

Re: 3.19.10 Release Breaks My Build

2024-06-19 Thread Lukas Eder
I've created this issue: https://github.com/jOOQ/jOOQ/issues/16842 On Wed, Jun 19, 2024 at 6:06 PM Lukas Eder wrote: > OK, I get it now. > > Before 3.19.10, we just didn't register any source sets at all, if there > was no main source set. > > I'm assuming, you manually added the output direct

Re: 3.19.10 Release Breaks My Build

2024-06-19 Thread Kevin Jones
Hey Lucas, thanks for looking into this so quickly. This is the repo https://github.com/kevinrjones/jooqtest The line that's causing the issue is in the root build.gradle file: I have this: tasks.withType() { compilerOptions.jvmTarget.set(JvmTarget.JVM_21) dependsOn(tasks[

Re: 3.19.10 Release Breaks My Build

2024-06-20 Thread Lukas Eder
Thanks a lot for the reproducer, Kevin, that certainly helps save time and regression-test this particular case. At least, until my next wrong assumption about how gradle works is exposed 😅 On Wed, Jun 19, 2024 at 8:58 PM Kevin Jones wrote: > Hey Lucas, > > thanks for looking into this so quick

Re: 3.19.10 Release Breaks My Build

2024-06-20 Thread Lukas Eder
In any case, the workaround should be to explicitly create the main source set in your build script, yes? On Thursday, June 20, 2024 at 10:53:52 AM UTC+2 Lukas Eder wrote: > Thanks a lot for the reproducer, Kevin, that certainly helps save time and > regression-test this particular case. > > At

Re: 3.19.10 Release Breaks My Build

2024-06-20 Thread Kevin Jones
That should work. I’ll give it a go when I’m back at my computer, Kevin Jones KnowledgeSpike On Thu, 20 Jun 2024 at 14:36, Lukas Eder wrote: > In any case, the workaround should be to explicitly create the main source > set in your build script, yes? > > On Thursday, June 20, 2024 at 10:53:52 

Re: 3.19.10 Release Breaks My Build

2024-06-24 Thread Lukas Eder
I can confirm, this definitely works around the issue: sourceSets { create("main") } In the meantime, https://github.com/jOOQ/jOOQ/issues/16842 has been fixed for 3.20.0 and 3.19.11. Thanks again for your report and reproducer. The reproducer will be helpful in preventing any regressions for

Re: 3.19.10 Release Breaks My Build

2024-06-24 Thread Kevin Jones
Hey Lucas, Thanks for your quick response, as always, Kevin Jones KnowledgeSpike On Mon, 24 Jun 2024 at 08:20, Lukas Eder wrote: > I can confirm, this definitely works around the issue: > > sourceSets { > create("main") > } > > In the meantime, https://github.com/jOOQ/jOOQ/issues/16842 has