Java – Error while installing Maven Integration for Eclipse

eclipseeclipse-pluginjavam2eclipsemaven

I'm trying to install Maven integration for Eclipse (Galileo) through Install New Software menu nad using the sonatype link

http://m2eclipse.sonatype.org/sites/m2e

And getting following error:

Cannot complete the install because one or more required items could not be found.
Software being installed: Maven Integration for Eclipse (Required) 0.12.0.20101115-1102 (org.maven.ide.eclipse.feature.feature.group 0.12.0.20101115-1102)
Missing requirement: Maven Integration for Eclipse (Required) 0.12.0.20101115-1102
(org.maven.ide.eclipse.feature.feature.group 0.12.0.20101115-1102) requires 'org.eclipse.emf.ecore.edit 0.0.0' but it could not be found

Tried to search for the missing bundle. But no success. 🙁

Any help?

Best Answer

In your install manager, check "Contact all updates sites..." and try again. Since EMF comes from a different update site than M2Eclipse, M2Eclipse cannot be installed without the ability to check all update sites for required components.

UPDATE!

Since Eclipse 3.7 (Indigo), m2e is now hosted at eclipse.org. To install it, you just need to use the default Eclipse update site:

Related Solutions

Android – “Debug certificate expired” error in Eclipse Android plugins

Delete your debug certificate under ~/.android/debug.keystore on Linux and Mac OS X; the directory is something like %USERPROFILE%/.androidon Windows.

The Eclipse plugin should then generate a new certificate when you next try to build a debug package. You may need to clean and then build to generate the certificate.

Eclipse – How to solve “Plugin execution not covered by lifecycle configuration” for Spring Data Maven Builds

In my case of a similar problem, instead of using Andrew's suggestion for the fix, it worked simply after I introduced <pluginManagement> tag to the pom.xml in question. Looks like that error is due to a missing <pluginManagement> tag. So, in order to avoid the exceptions in Eclipse, one needs to simply enclose all the plugin tags inside a <pluginManagement> tag, like so:

<build>
    <pluginManagement>
        <plugins>
            <plugin> ... </plugin>
            <plugin> ... </plugin>
                  ....
        </plugins>
    </pluginManagement>
</build>

Once this structure is in place, the error goes away.

Best Answer

Related Solutions

Android – “Debug certificate expired” error in Eclipse Android plugins

Eclipse – How to solve “Plugin execution not covered by lifecycle configuration” for Spring Data Maven Builds

Related Topic