Hello, Thank you very much for your detailed report.
2017-02-16 4:11 GMT+01:00 <[email protected]>: > We had an odd one tonight. We were finally in a good space to do an > upgrade and be able to do a full regression test of our platform. > > Moving from jOOQ 3.7.4 to 3.9.1 causes all sorts of weird compile issues > in Eclipse. We did do a refresh of the project (gradle - buildship). A > few errors would came up about .eq() method no longer matching the String > values in there. Ok, easy enough to fix... but as soon as we touched the > files 100+ error showed up saying that all of our staticly imported Tables > are no longer available. Odd! > > First the fix for the .eq() methods was that we were actually now > generating .enum.TableEnum packages (which we were not before). So the > .eq("String") just changed to .eq(TableEnum.ENUM). easy fix. > That is interesting. I suspect that it is related to what you wrote below... > For the odd compile and static errors we had to turn on > globalTableReferences = true in our generator. Another odd one since it's > defaulted to true. > I had reported this issue to Etienne Studer (maintainer of the Gradle plugin by Gradle Inc.) in the past. He mentioned to me that the plugin doesn't alter or specify any defaults: https://github.com/etiennestuder/gradle-jooq-plugin/issues/9#issuecomment-151274741 But quite possibly, this isn't true. I've had a look through the plugin's code and I think that the default values as specified in the XSD specification are not maintained by the plugin: https://github.com/etiennestuder/gradle-jooq-plugin/issues/9#issuecomment-280606954 I invite you to join that discussion on GitHub if you have any further information / examples on how to reproduce this. > Cleaned all of the projects, re-generated all of the jooq code and viola > all worked perfect. Still need to go through the tests which takes a week > of on/off work but all of the automated tests worked. > > Below is a summary of the gradle build script changes in case anyone else > runs into something similar: We import the jooqBuilder.gradle script > externally. > > build.gradle: > > plugins { > - id 'nu.studer.jooq' version '1.0.6' > + id 'nu.studer.jooq' version '2.0.3' > Indeed, I believe that a lot has changed between versions 1.0 and 2.0, specifically with respect to mapping the gradle config objects to jOOQ's XJC-generated JAXB-annotated Configuration object. Hoping that this will explain the issue. Thanks again for your detailed bug report, greatly appreciated! Lukas -- 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.
