Hello Eric, Yes, that about describes the problem. So I'm just curious how to best solve this. In principle, the strategy shouldn't be in src/main/java, but in some other folder that can be compiled before generating the sources.
If adding a new project can be avoided, all the better Cheers Lukas 2012/4/26 ericjs <[email protected]>: > I'm definitely no maven expert, but I wonder if this is something of > circular dependency problem. If the custom strategy were in a > different project then it could be a dependency of the plugin, but if > it is in the same project...well I'm not sure how that works. At the > very least it seems to me that this would mean that the phase in which > the jooq codegen occurred would have to be a phase AFTER the compile > of the project code; and I assume that project code also would > dependitself uses the jooq generated classes which requires the > opposite. > > On Apr 25, 3:13 pm, Lukas Eder <[email protected]> wrote: >> I've recently had a good question here about how to use the >> jooq-codegen Maven plugin with a custom generator >> strategy:https://sourceforge.net/apps/trac/jooq/ticket/1355 >> >> I raised the issue on Stack >> Overflow:http://stackoverflow.com/questions/10322155/how-to-use-a-custom-strat... >> >> Any ideas by the "Maven pros" on this list welcome! (feel free to >> answer directly on Stack Overflow) >> >> Cheers >> Lukas
