It is now official. A posting from the official Android Developer’s blog has confirmed what many of us already knew, that the days of the original Android Developer Tools based on Eclipse was numbered. Honestly, I think this is not a bad thing. It does free up the resources that Google has to fully concentrate on the Android Studio tooling, and continue to improve and advance their chosen strategy going forward.
However, all is not lost, as the Andmore project is here to continue to provide Android tooling for the Eclipse community. However, progress right now is pretty slow, and that is because my own time has been limited. With this said, we do have integrated support with Maven and the android-maven-plugin through the m2e-android project’s support. The Buildship project can import an existing Android gradle project, and even run some tests, but it still has problems in setting up the project natures and make things work with Andmore. There is a feature request opened to have some sort of project configuration extension so that Andmore can help configure such projects to better work with the tooling.
The state of Android development with Andmore and how well it keeps up with the yearly and quarterly updates coming from the Android Open Source Platform is going to greatly depend on contributions from the community. We need your help, as one person definitely can not maintain the project alone. So please do take a look at the bug/feature backlog, feel free to fork the project on GitHub, roll up your sleeves and get a bit dirty, submit pull requests and file new bugs. Andmore is going to be what the community makes it. We wished for years that ADT had been open more to contributions from the community, now is the time for us to follow through on that wish.