The suggestion to get code generation working is to add something like
the following to a parent-pom or to the pom.xml where cxf codegen is
happening:
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>your group id</groupId>
<artifactId>your plugins artifactid</artifactId>
<versionRange>[minimum version number,)</versionRange>
<goals>
<goal>goals to support</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute />
</action>
</pluginExecution>
</lifecycleMappingMetadata>
</configuration>
</plugin>
Put the above under your pluginManagement entry in your pom. It will at
least allow codegen to run, but it won't add the source folders.
Dave
On 06/24/2011 11:54 AM, Christian Schneider wrote:
I also get the same error when using the cxf codegen plugin.
Plugin execution not covered by lifecycle configuration: ...
I have pasted my config below.
The problem is that m2eclipse does not generate the code now and so my
project does not work.
In the old version of m2eclipse (from sonatype) I could execute
"update project configuration" which triggered the code generation.
So can I somehow generate the code and configure eclipse for the
source dirs with the new m2eclipse version from Indigo?
I already thought the old behaviour that "update project
configuration" was necessary was not ideal and hoped that the new
version could
simply work with the cxf code gen.
I wonder why a lifecycle plugin is necessary. Can´t this simply be
solved generically. I mean it works when doing mvn eclipse:eclipse so why
should it not work in m2eclipse?
Christian
---------------
<plugins>
<plugin>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-codegen-plugin</artifactId>
<version>${cxf.version}</version>
<executions>
<execution>
<id>generate-cxf-sources</id>
<phase>generate-sources</phase>
<configuration>
<wsdlOptions>
<wsdlOption>
<wsdl>${basedir}/src/main/resources/CustomerService.wsdl</wsdl>
<bindingFiles>
<bindingFile>${basedir}/src/main/resources/binding.xml</bindingFile>
</bindingFiles>
</wsdlOption>
</wsdlOptions>
</configuration>
<goals>
<goal>wsdl2java</goal>
</goals>
</execution>
</executions>
</plugin>
Am 24.06.2011 12:45, schrieb Moser, Christian:
Just tried out our build environment with Indigo and m2e
1.0.0.20110607-2117.
User-experience :
After a full import of all maven projects, I've received following
error in almost every pom:
Plugin execution not covered by lifecycle configuration: ...
After clicking around for some time, I found under pom.xml / Overview
the possibility to ignore those «not covered plugin-lifecycles »
--
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Divisionhttp://www.talend.com
_______________________________________________
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
