Ok, thanks ! Le lundi 29 septembre 2014 18:20:36 UTC+2, Lukas Eder a écrit : > > You're right, that's a bug. I have registered an issue for this: > https://github.com/jOOQ/jOOQ/issues/3655 > > One way for you to circumvent that bug is to patch the maven plugin and > explicitly close the JDBC connection that is used in there. Another > workaround would be to use dedicated profiles for generating source code in > order to keep code generation isolated. > > Hope this helps, > Lukas > > 2014-09-29 13:41 GMT+02:00 <[email protected] <javascript:>>: > >> Hello, >> >> I am using a derby embedded database for evaluating jooq. On this >> database, I can only have one open connection. >> >> I have an issue with the jooq codegen maven plugin, it seems that the >> plugin doesn't close the connection before starting unit test. >> So, when maven run my units test, it throw an exception that a connection >> is already open. >> >> Do you know why ? >> >> Thanks for your help. >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > >
-- 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]. For more options, visit https://groups.google.com/d/optout.
