How to disable m2e build in Eclipse Indigo?
Asked Answered
S

4

1

I'm currently using Eclipse Indigo in an Android project that I'm working on and am running into problems with the built-in Maven (m2e) builder. I use the ADT plug-in to build the project, but I also have a Maven pom.xml that's used to build the project from the command line. Once I switched from Helios to Indigo, I started seeing these errors:

Plugin execution not covered by lifecycle configuration: com.jayway.maven.plugins.android.generation2:maven-android-plugin:2.9.0-beta-5:generate-sources (execution: default-generate-sources, phase: generate-sources)

Plugin execution not covered by lifecycle configuration: com.jayway.maven.plugins.android.generation2:maven-android-plugin:2.9.0-beta-5:unpack (execution: default-unpack, phase: process-classes)

Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar (execution: default-jar, phase: process-classes)

My goal is to keep the Maven build separate from the ADT Eclipse build so I'd like to simply disable m2e for the project but I can't figure out how to do that.

Is there a way to disable the m2e builder? Alternatively, is there a way to fix the above errors?

Severson answered 11/8, 2011 at 15:46 Comment(2)
Have you looked into Project -> Properties -> Builders? Maven builder might have been registered there.Hera
@Hera That was my first thought too, but there are no Maven builders displayed.Severson
N
5

Open your POM and click on the "Plugin execution not covered by lifecycle configuration" error. This will give you the option to Discover new m2e connectors.

Select this and you should be automatically prompted to download and install the Android Connector.

Installing this should resolve your problems. You should probably uninstall the old 0.2.4 m2eclipse-android-integration as well in favour of the new 0.3.0 m2e-android version.

Please see the new site for more information:

http://rgladwell.github.com/m2e-android/

Neoplasty answered 11/8, 2011 at 21:6 Comment(0)
J
1

M2E official wiki documents this issue

I think you can use lifecycle-mapping plugin from m2e to silently ignore the execution for these plugins

Janiculum answered 11/8, 2011 at 18:2 Comment(1)
You do not need to do this, your Android project will ignore Maven dependencies. Please simply install the Android Configurator for M2E. See my answerNeoplasty
E
1

I went into my install directory for Eclipse and manually removed all the references to m2e. There were multiples in the "Plugin" directory and the "features" directory. After that my android project was back to behaving like normal and I could use mvn from the command line to build.

Eddie answered 17/1, 2012 at 23:27 Comment(0)
S
0

I am using MacOSX with Eclipse 4.3 (Krepler). What I originally tried was to install Maven via the terminal using Brew. It installed correctly Maven 3.0.4. However when I tried to import any ready maven projects (File > Import > Maven) it would display the following two errors:

No marketplace entries found to handle Execution default-testResources

What I did is go to Help > Eclipse Marketplace and type "Maven" in the search bar and install the first default Maven client for Eclipse. Everything worked for me from this point.

Hope it helps to you too.

Shrievalty answered 19/7, 2014 at 11:24 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.