I am not sure I understand the problem. Does your command line build reformats java code (or validates java code format), or these actions are strictly m2e specific and have no command line build counterparts?
-- Regards, Igor On 11-09-30 11:06 AM, Sascha Vujevic wrote:
Hello users, i have a question about the m2e 1.0 lifecyclemanagement: we need to execute configurators on maven-projects which e.g. formats java-code or make save-actions on these projects. These executions are normally not attached to maven-plugins. How can i attache these configurators (own plugins) to m2e. Is there a possibility to atache more then one configurator to one maven-plugin: <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <versionRange>[1.0.1,)</versionRange> <goals> <goal>enforce</goal> </goals> </pluginExecutionFilter> <action> <id>own.maven.ide.eclipse.configurators.scm.cleanup</id> </configurator> <configurator> <id>own.maven.ide.eclipse.configurators.scm.saveactions</id> </configurator> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> Thank you for your help an have a nice week. Best regards Sascha Vujevic _______________________________________________ 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
