Enabling workspace build and especially incremental build for maven plugins that were not specifically coded to support this mode of operation is asking for troubles. Missing generated resources is one problem you're going to face, but be prepared to see endless build loops and workspace crashes too, see [1] for some background information and possible ways to implement Joog/m2e code generation support.
[1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered -- Regards, Igor On 12-03-04 8:43 PM, Ian Clarke wrote:
I'm trying to set up the Jooq database mapping library, part of which involves generating Java sources based on a database schema. I've followed all available instructions on setting this up with Maven, and I now have it to the point that I can run this at the command line: mvn generate-sources And it will do what it's supposed to do. I'm also using the build-helper-maven-plugin to add the generated sources to the build path, and this now works with M2E. The problem is that I can't seem to persuade M2E to generate these sources as part of the normal build process within Eclipse. When I delete target/ at the command line it fails to regenerate the source, and then complains about not being able to find those generated files. I've added a pluginExecutionFilter and set <action> to <execute> with <runOnIncremental>true</runOnIncremental>. Here is my pom.xml : https://gist.github.com/7def8d798830853a7d0b Can anyone offer any suggestions? Ian. -- Ian Clarke Blog: http://blog.locut.us/ _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
