Dear m2e community, when reading: http://wiki.eclipse.org/M2E_plugin_execution_not_covered#metadata_source_lookup_order
I thought, I could map a plugin like "axis2-wsdl2code-maven-plugin" to a Maven
lifecycle - here "generate-sources" to achieve getting a valid POM without the
following exception:
Plugin execution not covered by lifecycle configuration:
org.apache.axis2:axis2-wsdl2code-maven-plugin:1.6.2:wsdl2code (execution:
default, phase: generate-sources)
Am I wrong using the below configuration?
<plugin>
<groupId>org.apache.axis2</groupId>
<artifactId>axis2-wsdl2code-maven-plugin</artifactId>
<version>1.6.2</version>
<executions>
<execution>
<phase>generate-sources</phase>
<goals>
<goal>wsdl2code</goal>
</goals>
</execution>
</executions>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.apache.axis2</groupId>
<artifactId>axis2-wsdl2code-maven-plugin</artifactId>
<versionRange>[1.0.0,)</versionRange>
<goals>
<goal></goal>
</goals>
</pluginExecutionFilter>
<action>
<execute>
<runOnIncremental>false</runOnIncremental>
</execute>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
...
</configuration>
</plugin>
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
