Error importing Maven Android Android project to Eclipse with ADT 20-ThrowExceptions

Exception or error:

I’m updated the ADT plugin to the last version (20) and the android-sdk tool. Now when I try to import an existent Android Maven to Eclipse raise the exception An internal error occurred during: "Importing Maven projects".
, and creates the eclipse project but not like Android project as before. The previous existent (maven android) projects in the workspace works fine.

The Eclipse full exception trace when import the project is the following:

!ENTRY org.eclipse.osgi 2 1 2012-06-29 19:02:34.421
!MESSAGE NLS unused message: LifecycleMappingPropertyPage_this_message in: org.eclipse.m2e.core.ui.internal.messages

!ENTRY 4 2 2012-06-29 19:03:03.953
!MESSAGE An internal error occurred during: "Importing Maven projects".
java.lang.NoClassDefFoundError: com/android/io/StreamException
    at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(
    at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(
    at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProject(
    at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(
    at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$1.doCreateMavenProjects(
    at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$3.runInWorkspace(
Caused by: java.lang.ClassNotFoundException:
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(
    at java.lang.ClassLoader.loadClass(
    ... 12 more

Can anybody solves it? Is needed an update of the m2e Android connector?

This my pom.xml:

<project xmlns="" xmlns:xsi="" xsi:schemaLocation="">

                        <!-- platform or api level (api level 4 = platform 1.6)-->


How to solve:

This is a known issue with the m2e-android plug-in caused due to changes in the ADT API:

Please be patient while we find a fix.

Update: The new 0.4.2 release fixes this issue was released today, please run an Eclipse update (Help -> Check for Updates) and let me know if this resolves your problems.


edit: Rather than do this, you might now be better off getting Ricardo’s updated project from github, switching to the adt-20 branch, building with Maven, uninstalling the M2E connector as described below, and installing the new M2E connector from as a local repository, also as described below. Thanks, Ricardo!

I had this problem and couldn’t build my project. The only way I got round it was to downgrade ADT to 18.0.0. I couldn’t find a way of doing this through the SDK Manager etc., so this turned out to be a bit of an ordeal – though I quite probably didn’t do it the most sensible way! Anyway, I thought I’d post what I went through in case it helps anyone. I left out the umpteen Eclipse restarts. 🙂

This was on Eclipse 3.7 on Linux.

  • Get the ADT zip:
  • Get the Android SDK Tools archive for your OS: (replace linux.tgz with or – sorry, Stack Overflow only allows me two links in my post!).
  • Disable automatic software updates: Window -> Preferences -> Install/Update -> Automatic Updates, uncheck ‘Automatically find new updates and notify me’.
  • Uninstall Android SDK Tools: Window -> Android SDK Manager, check Android SDK Tools and click ‘Delete 1 package’.
  • Uninstall ADT: Help -> Install New Software -> What is already installed? -> Installed Software, select all the Android* components and the Android Configurator for M2E and click ‘Uninstall’.
  • Extract and install: Help -> Install New Software -> Add -> Local and browse to where you extracted it. Give the local repository a name and click OK, then select it from the ‘Work with’ drop-down and install the available software from it.
  • Extract the tools directory from the android-sdk_r18 archive into your android-sdks directory.
  • Install Android M2E connector: Preferences -> Maven -> Discovery, click ‘Open Catalog’ then select the connector. Deselect any ADT 20.0 features if prompted.


Now the andriod maven connector it’s fixed to works with ADT 20+, only needs to install the update from the following update site:


Just open your file. XML and tab below the “Graphical Layout” (in the case of eclipse).
You still there locate the Android icon that is located on the top right that details the version that is used in my case was using version 18, I selected version 17 and the error disappeared.

Leave a Reply

Your email address will not be published. Required fields are marked *