You shouldn't need any plugin execution filter for maven-compiler-plugin, since it's taken care of by the JDT integration built in m2e. maven-compiler-plugin is skipped by default and compilation is delegated to JDT instead.
2013/7/4 Kristian Rink <kawazu...@gmail.com> > Am 04.07.2013 12:18, schrieb Fred Bricon: > > Have you enabled some maven plugins to automatically run during eclipse >> builds >> (http://wiki.eclipse.org/M2E_**plugin_execution_not_covered#** >> execute_plugin_goal<http://wiki.eclipse.org/M2E_plugin_execution_not_covered#execute_plugin_goal> >> )? >> That could cause some performance issues. >> > > Thanks for your hint. Actually, this is what got me out of trouble here. > Used to have an "<ignore/>" in a plugin-execution-filter for > maven-compiler-plugin and testCompile. Changing this to > <runOnIncremental>true</**runOnIncremental> made things work as expected. > Thanks vey much for getting me to a working state again! > > Cheers, > > Kristian > ______________________________**_________________ > m2e-users mailing list > m2e-users@eclipse.org > https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users> > -- "Have you tried turning it off and on again" - The IT Crowd
_______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users
