Hi Garret, Did you encounter this issue with jOOQ 3.3, i.e. with the latest version?
There had been a fix to correctly handle relative paths in the <directory> element: https://github.com/jOOQ/jOOQ/issues/2887 The fix was implemented in 3.3.0 and 3.2.3 Cheers Lukas 2014-04-27 23:39 GMT+02:00 Garret Wilson <[email protected]>: > The online > documentation<http://www.jooq.org/doc/3.1/manual/code-generation/codegen-configuration/>gives > the following as an example of how the output directory can be > indicated for generated files: > > <directory>target/generated-sources/jooq</directory> > > The result is less than correct, as this will unexpectedly output the > classes relative to the root project if called from a *subproject* in a > hierarchical Maven configuration. > > I could make a wild guess and say that this is probably a bug in the jOOQ > Maven plugin itself, resolving the given directory relative to the "current > directory" rather than first requesting the current project directory from > Maven and then resolving the given directory to that. However, one can work > around this bug by using the following: > > <directory>${project.build.directory}/generated-sources/jooq</directory> > > -- > 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. > -- 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.
