This is now fixed for jOOQ 3.6.0 and will be merged to older jOOQ versions: https://github.com/jOOQ/jOOQ/commit/2b06039e505134f79ef770043e87b436394082ae
Cheers, Lukas 2015-02-16 14:44 GMT+01:00 Lukas Eder <[email protected]>: > > > 2015-02-16 14:25 GMT+01:00 <[email protected]>: > >> I asked you once when the 3.6 release was planned, and you more or less >> told me that it will take many months. >> I'm not just trying JOOQ but plan to use it in production, if it helps >> me, quite soon. That being considered, I can't plan to release a Java >> artifact built upon a SNAPSHOT release (maven won't love it anyway). >> > > I understand. > > >> It that bug is fixed in 3.5.3, that should be enough for me to work. >> > > Well, let's hope it can be done. :) > > >> Recurring question: when that version has a chance to be born? :) >> > > "Probably" by the end of March. Certainly by April. > > >> BTW, I don't get something: you tell me that upgrading to 3.6 might help >> me, but you tagged the bug for the 3.6 milestone in you bug tracker. So I'm >> not sure of what the upgrade would bring me on that precise topic. >> > > Unfortunately, GitHub doesn't support tagging an issue with several > milestones. That is why we ususally create issues for a minor release, and > then create additional issues for the patch releases when we see that > something should be merged. > -- 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.
