You need a project configurator. <execute/> mapping is the last resort thing and is not expected to work for any mojo that generates workspace resources.
http://wiki.eclipse.org/M2E_plugin_execution_not_covered -- Regards, Igor On 12-07-09 5:13 PM, Markus Karg wrote:
Hello m2e Community! My pom.xml enables execution of the xml-maven-plugin (and enables generated-sources as a target folder using the build-helper-plugin): <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId>org.codehaus.mojo</groupId> <artifactId>xml-maven-plugin</artifactId> <versionRange>[1.0,)</versionRange> <goals> <goal>transform</goal> </goals> </pluginExecutionFilter> <action> <execute/> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> After pressing F5 I can see the generated outcome in Eclipse Indigo. Nice! J But I don’t want to press F5! So how to tell m2e that after <execute /> of the plugin, it also shall <refresh /> the generated-sources folder in the IDE? Thanks! Markus _______________________________________________ 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
