Google will no longer support Android Eclipse Tools and androideclipse

Google will no longer support Android Eclipse Tools and androideclipse

This article is from the article I translated on InfoQ Chinese site, the original address is: http://www.infoq.com/cn/news/2015/06/Building-Distributed-Systems

Recently, Google announced that it will stop all support for Eclipse Android development tools by the end of the year.

When Android Studio 1.0 was released, Google announced that it would be the official Android development tool and recommended that developers switch to Android Studio. For developers who have not yet switched to Android Studio, they have to face this problem because Google has announced that it will end the development and support of Eclipse Android tools by the end of this year. This includes the ADT plug-in, Ant build system, DDMS, Traceview, and other performance and monitoring tools.

To migrate from Eclipse to Android Studio, read this migration guide to understand the new project structure and how to build Android projects through Gradle. If the prerequisites are met, you can use Android Studio to import the Eclipse project and then perform verification (build and run) to ensure that everything is correct. If there is any problem, Google recommends adjusting the Eclipse ADT project and then importing it again.

It is recommended that developers who want to continue using Eclipse look at and participate in the Andmore project, which aims to enable the Android tool to continue to play a role in Eclipse. Andmore includes JDT, CDT, and ADT, supports Maven and Ant, and plans to provide support for Gradle, which can now be integrated with Mylyn, EGit and GitHub.

As we all know, Google has launched many projects and put forward many bold innovations, but many times it will easily kill a project that proved unfeasible, reader, Wave, Buzz, Knol, Code, Dart Editor, and Chrome Dev Editor. This is very different from the practice of many software developers, who will follow up on those less motivated projects to ensure that the project can reproduce its vitality. Although Google's flexible practices have been integrated into the company's DNA, many development communities still feel uncomfortable about this. We have seen a lot of comments from developers who are reluctant to participate in new Google projects, because they are worried that the projects will be terminated in a few days, delaying the usage of such projects. Should Google change the way they do things, or should developers be more flexible?

View Original English text:Google Ends Support for Android Eclipse Tools