Re: [m2e-users] feedback M2E Ingio - m2e connector concept

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

see my comments inline.

--
Regards,
Igor

On 11-06-24 7:54 PM, 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.

This can "simply work", provided m2e 1.0 gets some help.

For 1.0, this means somebody has to write a relatively simple m2e
extension and we are documenting how to do this in [1]. Longer term we
are looking for ways to simplify this even further, likely by extending
build lifecycle mapping metadata format to support code generation as a
special case. We track this enhancement request as [2].

> 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?

I believe this is the only way to properly and reliably integrate maven
build in Eclipse workspace. I provided more detailed explanation on this
least earlier, see [3] and [4] for example

[1] http://wiki.eclipse.org/M2E_Extension_Development
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=335711
[3] http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00572.html
[4] http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00585.html



> 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
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users