Google Ends Support for Android Eclipse Tools

| by Abel Avram Follow 7 Followers on Jun 27, 2015. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Google has announced the end of all Eclipse-based tooling for Android development by the end of the year.

When Android Studio reached version 1.0, Google declared it the official Android development tool, suggesting developers to switch to it. Those who have not done it so far, now have serious reasons to do it because Google has announced the termination of development and support of Android tools in Eclipse at the end of 2015. This includes the ADT plug-in, the Ant build system, DDMS, Traceview, and the rest of performance and monitoring tools.

To make the switch from Eclipse to Android Studio, it is recommended to read the migration guide to understand the new project structure and how Gradle works for building Android projects. After the prerequisites are met, Eclipse-based projects can be imported with Studio, followed by a validation (build and run) to make sure everything is all right. If there are problems, Google recommends tweaking the Eclipse ADT project and importing again.

Those still wanting to stay with Eclipse are recommended to follow and contribute to the Andmore project, an attempt to continue the presence of Android tooling in Eclipse. Andmore includes JDT, CDT, ADT, it supports Maven and Ant, it has plans for Gradle support, and is integrated with Mylyn, EGit and GitHub.

Google is known for starting many projects, announcing many bold initiatives, but then easily killing a project that turns out as being not viable, as it was the case with Reader, Wave, Buzz, Knol, Code, Dart Editor, or Chrome Dev Editor, to name a few.  Their approach is quite different from that of many software developers who tend to artificially keep alive a project that has not got traction. While Google’s flexibility seems to be woven into the company’s DNA and provides a level of agility, some in the development community are not confortable with this approach. We’ve seen numerous comments from developers reluctant to join new projects from Google being afraid these will be terminated after a while, slowing down the adoption of such projects. Should Google change their approach or developers become more flexible?

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

An ironic comment by Diego Visentin

I suspect that Google has the "not invented here" disease :-|

Re: An ironic comment by David DeCesare

I'm not sure what you mean. The Android Studio IDE is based on IntelliJ IDEA ( so it's still based on someone else's product. It just happens to be IntelliJ rather than Eclipse.

Re: An ironic comment by Diego Visentin

You are right, but I suspect that the choice depends more on the possibility of ruling a small software house instead of a foundation made by major IT players. But maybe I just do not understand the real reason for the choice.
PS: I'm an Eclipse user from before it was called Eclipse, so I'm not totally objective ;-)

Re: An ironic comment by Abel Avram

Google is very pragmatic. They go for the tools and processes they believe have the greatest benefit. In this case they settled for IntelliJ-based IDEs, not just for Android development, but for other technologies as well, such as Dart. They have not said exactly why, and they did not criticize Eclipse, but we can suppose it is because of IntelliJ's license, the community edition allowing them to develop tools on top of it at their own speed without having to wait on anyone. They did the same with WebKit. Since Apple was not flexible or fast enough, Google forked it as Blink and now goes ahead at full speed.

Flexibility by Mauro Molinari

"We’ve seen numerous comments from developers reluctant to join new projects from Google being afraid these will be terminated after a while"

Maybe I'm one of them, after seeing how they have driven the GWT development...

"Should Google change their approach or developers become more flexible"

The problem is that probably not all developers have time and resources to be "flexible", in the sense of being *constantly* ready to change tools and learn new technologies. "Sometimes" you just have to do your work while learning how to do it well, and invest on something which should last for at least some years... Not all companies are like Google, which can afford this attitude. Just my opinion.

Who cares by Ivan Gavryliuk

Google made Android development too hard, their api don't make sense and require just too much of development time wasted. For that reason many switch to Cordova or Xamarin anyway (you should consider it at some point if you want the company to be profitable and apps not awfully fragmented). I think raw java for Android only only needed by framework developers, they can cope!

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

6 Discuss

Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you