Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] feedback M2E Ingio - m2e connector concept

I will have a look at it. Perhaps I can write this for cxf codegen.

The question is why can´t we simply execute the plugins and then refresh the eclipse project. It does not have to be
automatically. Just on import and then on demand. Also mvn install picks up the source directories the generation creates. So I don´t get why we have to provide more code.

Christian


Am 24.06.2011 18:08, schrieb Matthew Piggott:
If you're interest in writing code to enable it for Eclipse, you might take a look at: https://github.com/sonatype/m2eclipse-extras


On 24 June 2011 11:54, Christian Schneider <chris@xxxxxxxxxxxxxxxxx> 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 Division http://www.talend.com

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users


_______________________________________________ m2e-users mailing list m2e-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/m2e-users

-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Back to the top