Re: [ide-dev] Some Java dev stories where Eclipse > IDEA
Great work, Doug. As soon as the JDT classpath can be set based in the Android Gradle dependencies, the majority of Android dev should already work.
I already use most of the time Eclipse Buildship to execute Android tests created in AS as the result view is much nicer in Buildship then in AS.
The different classpath scopes in Android Gradle (main/test/androidTest) may be a challenge I think the only practical solution is to put all of the dependencies into the JDT classpath.
Best regards, Lars
Am 26.01.2016 6:53 nachm. schrieb "Doug Schaefer" <cdtdoug@xxxxxxxxx
Thanks Mickael. Love the retweets you sent out from people who have a lot of hate for Android Studio versus Eclipse. I played with Studio quickly and found it really dumb. I guess there are some good features once you get used to it but I've been using Eclipse so long I'd hate to have to use something else, especially if it means switching back and forth to do things that Studio doesn't do, like Arduino or Raspberry Pi.
So to update the crowd on this list, I've started a reboot of the Android tooling for Eclipse, an Andmore2 if you like. It uses the Android Gradle build system and build model at the start and we'll go from there. As we need we'll bring the features we have in Andmore1 over.
There's no kidding ourselves that this is going to take a while, especially since it's just me as a side project but with guidance from Android tooling experts. But I don't think it'll take long before we have something that can round trip from project creation to debugging. I should have that ready to demo by EclipseCon. My hope is that if we have something new, simple, clean that it will attract those Android Studio haters to help finish it and get Android back into the Eclipse fold.
ide-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit