It does seem like something worth reporting to IntelliJ, though I recall
how slippery the implementation of a lazy configuration was, so it won't
hurt to investigate if the 3.19.6 plugin now does something "stupid." The
current logic to register the code generation output directory with the
source sets is this, in CodegenPlugin:
https://github.com/jOOQ/jOOQ/blob/7e22b9818e785c2c5fc199de34476d3ac2890dae/jOOQ-codegen-gradle/src/main/java/org/jooq/codegen/gradle/CodegenPlugin.java#L111
task.doFirst(t -> {
SourceSetContainer source = project
.getExtensions()
.findByType(SourceSetContainer.class);
if (source != null) {
source.configureEach(sourceSet -> {
if (sourceSet.getName().equals("main"))
sourceSet.getJava().srcDir(task.getOutputDirectory());
});
}
});
Gradle has been an arcane mystery to me over these past months, so it may
well be that I'm still missing something "obvious" about when to do what.
On Thu, Mar 14, 2024 at 8:01 PM Pasha Finkelshtein <
[email protected]> wrote:
> It seems to me that if the build and everything else work correctly from
> the command line, then it's a bug in IDEA and it should be reported.
> Please report at https://youtrack.jetbrains.com/issues/IDEA
>
> Thank you in advance!
>
--
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/CAB4ELO5KL5F5H7PbGXve4cRK%3D6Eo%3DuGot8tCN577MFFJ33u60w%40mail.gmail.com.
