Using Eclipse for Android Development in 2016

May 15, 2016 • David Green

Using the best tool for the job has a direct impact to my overall sense of well-being and happiness - not to mention productivity. For me when it comes to Java, that means using Eclipse. Life is just too short for messing around. Eclipse has been relegated to the back benches for Android development now that Android Studio is based on IntelliJ. So what is an Eclipse die-hard to do?

I found that learning Android Studio was pretty straight-forward. I was up and running, creating a reasonable Android app within a couple of days, forcing myself to learn the “IntelliJ-way”, key bindings and all. After a couple of weeks rolled by, then months, I realized that my creativity was being hampered because I just couldn’t hit the flow in IntelliJ. The friction was affecting me: my code had fewer unit tests than I would like, and simple tasks were taking too long. IntelliJ was just slowing me down too much and it was impacting my project.

Seeing that Gradle buildship doesn’t yet support Android projects, A quick google for "Gradle generate Eclipse classpath" and I landed on this StackOverflow. With a few Gradle edits to build.gradle, I was able to generate the Eclipse .classpath and .project files needed to start editing Java source in Eclipse. My configuration is based on the answer provided by Johannes Brodwall: