Problems with m2e + Eclipse 3.7

[ntolia]

I just upgraded my environment to Eclipse 3.7 (Indigo) and the m2e plugin (using the 0.1.11 maven-thrift-plugin). m2e now complains about "Plugin execution not covered by lifecycle configuration" for the maven-thrift-plugin.

More information on this problem can be found at http://wiki.eclipse.org/M2E_plugin_execution_not_covered and, while one could always set the plugin to always execute, I think it might be better to "delegate". Any recommendations on what the preferred config should be? I am not completely familiar with how the thrift plugin/maven plugin ecosystem. Happy to experiment and report back on suggestions.

[Enrico2]

I see no one gave you an answer, did you manage to figure this out somehow? Thanks!

[flamholz]

Any news on this? I am interested as well.

[Enrico2]

I gave up. Switched to IntelliJ, after YEARS using Eclipse.

[MisterTea]

The problem is that eclipse wants an eclipse plugin to manage this maven plugin. Without someone to write that eclipse plugin, you will have this error.

one solution is to use eclipse as an editor but build from the command line.

[rflbianco]

I've faced the same problem and looking around I've found the solution. Even though it's not perfect, it's acceptable.

You'll need to add the following code to your 'pom.xml':

<build>
    <pluginManagement>
        <plugins>
            <plugin>
                <groupId>org.eclipse.m2e</groupId>
                <artifactId>lifecycle-mapping</artifactId>
                <version>1.0.0</version>
                <configuration>
                    <lifecycleMappingMetadata>
                        <pluginExecutions>
                            <pluginExecution>
                                <pluginExecutionFilter>
                                    <groupId>
                                        org.apache.thrift.tools
                                    </groupId>
                                    <artifactId>
                                        maven-thrift-plugin
                                    </artifactId>
                                    <versionRange>
                                        [0.1.10,)
                                    </versionRange>
                                    <goals>
                                        <goal>compile</goal>
                                    </goals>
                                </pluginExecutionFilter>
                                <action>
                                    <execute>
                                            <runOnIncremental>false</runOnIncremental>
                                        </execute>
                                </action>
                            </pluginExecution>
                        </pluginExecutions>
                    </lifecycleMappingMetadata>
                </configuration>
            </plugin>
        </plugins>
    </pluginManagement>
</build>

Adding this section to my 'pom.xml' the error was gone and I could execute the 'generate-sources' goal smoothly.

[yx1989]

So sad, 4 years past, the problem still exists.

[ksader-edmunds]

Has this been reported to Apache? All maintenance has been taken by ASF.

[MisterTea]

the reason why the problem still exists is because most people interested/capable of fixing the problem have already ditched maven for gradle.

[yx1989]

As MisterTea said, actually this problem is belong to m2e plugin on eclipse. I found a bug report in eclipse too, https://bugs.eclipse.org/bugs/show_bug.cgi?id=413776。 Some one replay: "Connectors for various maven plugins aren't part of the m2e project. See http://wiki.eclipse.org/M2E_Extension_Development".