On Wed, Nov 11, 2020 at 8:28 AM Maurizio <[email protected]> wrote:

> I'm sorry you could not reproduce the bug. I thought this was easy.


It probably is, but after several emails, I still couldn't get it to
reproduce, while my queue is also quite full at the moment. The Kotlin
integration is quite new and there are a few more obvious and pressing bugs
than this one. I still want to try to reproduce and fix it, but I need to
be able to reproduce it first.


> As promised, I'll try and package the code as a fork of the *jOOQ-mcve*
> repository. I delayed because I'm not familiar with Maven, and I'm a bit
> cognitively overwhelmed, currently, but I should be able to do it.
>

So, it's a stalemate :) The template allows for immediate reproduction, so
from experience, I tend to think it's worth it. This is already the 12th
email in this thread (and there are other threads). When bugs reported
through the template usually require a single email or github issue. I
believe that while it may take some time to get into, it does save time on
both sides (and it's also often helped find out user errors, which aren't
actual bugs, which I don't think is the case in your case).

Anyway, how can we have improved the template for you? One thing I will do
immediately is configure also KotlinGenerator and ScalaGenerator to work
out of the box, to get help prevent having to set up all the compiler and
library dependencies

-- 
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/CAB4ELO7E9P6NZH%2BfsT0Zv7VitfBcv-%3D0P-mec1md4%3D9exg%3Dq2Q%40mail.gmail.com.

Reply via email to