Android Developer Tools is dead….long live Andmore.

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.

Posted in android, eclipse | Tagged , | Leave a comment

Andmore 0.5-M1 Released

Screen Shot 2015-04-19 at 4.44.52 PM

Android development using eclipse has taken a step forward today.  The first stable milestone release is ready for you, the user community to kick the tires, and start to use for your development.  Full details can be found in the New and Noteworthy section for the release notes.

There is a p2 site for your installation needs, and it is recommended that you not install both Android Developer Tools and Andmore into the same IDE.

Add the above url to your available software sites.

Andmore contains all the functionality and features of Android Developer Tools, plus a lot more.    Also, thanks to Ricardo Gladwell for updating the m2e-android plugin to support Andmore.  This means that if you are using maven already, you can continue to do so with Andmore to continue developing Android applications and manage your dependencies.  The p2 site for maven support is:

So what about Gradel support and the the android gradle plugin?  Right now this is targeted for 0.5-M2.   There is a lot of stuff that needs to occur in order for this to happen.  For one thing, AAR support is necessary.   We also need to look into what extension points that the Buildship project will offer.  Will Andmore need to provide any extension points to allow Maven and Gradel to have more control over the build process?

Limitations with the current Andmore release:

  • No AAR support
  • No Gradel support
  • Android API 22 has limited support.  The only piece that may give you an error message is the GUI Layout editor.  If this happens change the API level in the editor from 22 to 21 or lower.

There is plenty to do yet, and the project is very open to contributions from the community.  If you would like to help out with any of the remaining work, do not hesitate to fork the repo on Github, and submit a pull request.   Andmore will be what the community makes it.  Bugs and Feature requests can be opened at:

Posted in android, eclipse | Tagged , | Leave a comment

Andmore 0.5-M1 RC2

Release Candidate 2 is available for smoke testing.   This is mainly some spit and polish to remove the Andmore name from the menus and views, and replace them with more generic labels where it makes sense.

Just add the above to your Install Software, and select the Andmore features to install.  Note that if you have existing ADT projects that you want to work with Andmore, you will need to Configure those to work with the new tooling.  To do so select a project, Configure->Convert ADT project.

If no new big show stoppers are reported by next week, we will do a formal 0.5-M1 announcement with complete change log.

Posted in android, eclipse | Tagged , | Leave a comment

Andmore 0.5-M1 RC1

We are getting close to having a 0.5-M1 p2 site ready for the general public.  There is a p2  release candidate available for testing:

The most important change is the implementation of bug 463598.  This allows you to convert existing ADT projects so that Andmore tooling can work with them.   To do this, select an existing ADT Project, and open the context menu.  Then select Configure->Convert to Andmore project.

This will update the project with the new nature and container ids.

Some users have started to submit some other bugs that will be addressed before we make 0.5-M1 official.  In the meant time, please try Andmore out, and report any usability bugs, or even consider providing some patches.

Posted in android, eclipse | Tagged , | Leave a comment

Importing existing Android Code into Andmore

Wayne raised a bug about importing existing Android Development Tools projects so they work with Andmore.   The problem arises because the various nature and builder ids have been renamed when we moved to Eclipse.  If we didn’t and you had ADT and Andmore installed in the same instance (this is just crazy talk why would one want do such a thing), then both Andmore and ADT would both be trying to control the project along with trying to build it.   Mass chaos would occur, and dogs and cats would be sleeping together.  Mass hysteria would occur.

To avoid this world ending situation, the ids were renamed.  It’ll be ugly but you could technically install both into the system, however I don’t recommend it.   You are better off just installing one or the other.  We hope it is Andmore.   If you do, how do you get your existing code brought into the system.

Luckily, there is an Import Wizard that can do the vast majority of the heavy lifting for you.  I’ve created a FAQ entry that outlines the steps.

This will take a project that is in the existing ADT format, and bring it into an Andmore workspace and set the builder and nature ids appropriately.   It does not work too well yet with Android Studio and Gradle related projects.   We need to make it a bit smarter in this area.

There are a couple of new bug reports to add support for these formats.

There is also a need to deprecate the APKLib format but still be able to import the appcompat_v7 libraries until AAR support is added.

Long term, APKLibs and the legacy project format need to go away, so that build tools like m2e-android, buildship, and others can add the necessary support and configuration for their project structures.   Andmore should provide the extension points where necessary so that you can plug in your own providers for these situations.

If you are looking for something to help out with, consider contributing a patch for bug 463610 and 463598 to help people migrate to Andmore from ADT.

Posted in android, eclipse | Tagged , | Leave a comment

Andmore Nightly p2 Repository

Andmore now has a nightly p2 repository available for Adopters and third party tool providers to start making use.

This site should contain everything you need to install Andmore into an eclipse environment and start developing android applications.  It can also be used by add on providers to build off and extend Andmore to other tools.   As with all nightly sites, this could be unstable at times, but should be useable to help provide feedback to the project.

Please help kick the tires and provide feed to the project about what is working and what isn’t working.  We need and want your involvement to help improve eclipse android tooling.

Posted in android, eclipse | Tagged , | Leave a comment

Andmore Planning for 0.5-M1

Finally unwinding from attending EclipseCon, and presenting the Andmore Project to the folks that are in attendance.   It is nice to see that there is still interest in having a first class set of tools that allow Android development.   I got to meet a lot of great people, and help get some pointed in the direction for code contributions.

One thing that is clear, is that we need to get you the community a p2 repo soon so that you can start kicking the tires and also start migrating tools that have been developed for ADT to also work with Andmore.   To this end, I have set myself the goal to get a 0.5-M1 build ready for you to use before the end of April.    This I believe should be doable and I will look at starting true nightly/integration builds for those that need them as well or just like to live on the edge.

To help those that are interested in contributing to Andmore understand where the dependencies with other eclipse projects come into play.  Below is a PDE Visualization of the dependency graph.


Andmore in particular is dependent on the platform, jdt, and the wtp projects.  Indirectly it pulls in other projects as well.   The org.eclipse.andmore project is the main plugin that many of the supporting plugins that andmore’s features depend upon.


Andmore itself is made up of a number of other plugins that provide additional functionality beyond just the base android project creation.    While the Android Core provides you with the basics of what you need, the additional plugins enhance the user experience.

Anyways, be looking for an 0.5-M1 build within the next month, and please consider forking the repository on github and providing some pull requests.

Posted in android, eclipse, eclipsecon | Tagged , | Leave a comment