Please forgive me if I'm rehashing something already considered, I just noticed this one and didn't see previous messages.
> - consider you use maven > - also consider that you mix jOOQ with something like > *brrr* hibernate / eclipselink / [any orm] > > -> chances are very, very high that the class names of > the entity classes (e.g. Customer.java -> mapped to > @Table "customer") will clash with the jOOQ generated > class 'Customer' when using the default strategy. Sure, but you could always generate the classes into separate packages. You may hit occasional issues with needing full qualification. The "Open Type" dialog in Eclipse isn't really a problem, you can type something like *pac*.Cu and you'll get classes with names like com.packaging.Customer. Not sure how this would interact with your Maven woes. I couldn't connect your problems to the situation you described (I probably missed something). The repository manager mention stuck out; my recent experience with Maven indicates that sooner or later, you'll be forced to use a repository manager anyway. I'm not sure that Jooq should accommodate merely postponing something that you'll have to do anyway. (I tried Maven recently, in the end decided it's too rigid to be adapted to the workflow and migrated to Gradle. Gradle came with its own set of road bumps, but in the end, it worked out okay.) Just my 2c. Regards, Jo -- 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/groups/opt_out.
