On Wed, Dec 30, 2015 at 5:16 PM, Lukas Eder <[email protected]> wrote: > The correct Maven phase for this would be generate-sources, or > generate-test-sources. > > Or am I misunderstanding something?
Depending on the level of customization I need to do with the code generation (e.g. weaving in custom bindings), I tend to split a flat Maven project into a multi-POM project so that the chicken and egg dependency resolution (i.e. app code depends on generated code that depends on custom code) is solved by each project producing a JAR for the next consumer. It's not elegant, but it is sometimes more pragmatic than fighting the Maven lifecycle. -- 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.
