Jon Bayle

Hi Lukas, Sure, for instance at this location: https://github.com/jOOQ/jOOQ/blob/59fe044378911cb48ff5df7375865dfef4fd3e49/jOOQ-codegen-gradle/src/main/java/org/jooq/codegen/gradle/MetaExtensions.java#L80 The action (a closure) is immediately applied and the outcome is stored. To make configuration lazy, the action should be stored...

You're right, making `NamedConfiguration.configuration(Action)` lazy would be sufficient to cover all cases.

Hi @FrontierPsychiatrist, This problem is in intellij, reported upstream: 1. https://intellij-support.jetbrains.com/hc/en-us/community/posts/18086275779730-IntelliJ-excludes-jooqCodegen-s-folder 2. https://youtrack.jetbrains.com/issue/IDEA-354580/IDEA-excludes-jOOQ-codegens-folder You'll find a workaround in the post on the community forum (1) until the intellij team addresses...

Hi @EAlf91, I cannot find the solution in the linked issue, could you please add a link to the specific comment? thanks!

Thanks @EAlf91, but imho, this is not a viable solution if we have to maintain a patched version of testcontainers.

Hi @frewsxcv, Sure, I'm interested in maintain this library, as we are to use this library in production very soon. What would I have to do?

Invitation accepted, thank you! One question: am I allowed to roll out new releases? and deploy to maven central?