I'm experiencing a very odd behavior when trying to upgrade the jooq version in a small project, and I was wondering if anyone could provide any insight.
I am currently using Jooq verion 3.5.1 without any problems and I tried to update to the latest 3.7.1 (seemed worthwhile lots of great features listed). When I bump up the version maven fails to return on the compilation step. It takes an abnormally long time to complete. For example: My project has 66 java files, there aren't really any class files that are 10K lines of code or anything out there. - with 3.7.1, Total time: 01:31 min - with 3.5.1 Total time: 2.144 s This behavior has started with Jooq 3.6.0, I can bump up the version all the way up to 3.5.4 and the project is still responsive, but when I go to 3.6 it completely unreasonable. I'm trying to pull jooq into a 'core' component that will be consumed by a larger project. So if the core just went from 3 seconds to 1.5 minutes I can't imagine being able to make this upgrade as it stands. Does anyone have any insights on what could be causing this, or any assistance in helping me debug this. As I said the only change I'm making is the version number on jooq, so I have a feeling something between what my project is using (lib wise), JVM version and Jooq itself is causing this, but I'd love some ideas on how to resolve this. -- Thank you Samir Faci -- 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.
