2015-05-26 11:36 GMT+02:00 Lars Vogel lars.vo...@gmail.com:
http://www.vogella.com/tutorials/EclipseGradle/article.html
Currently the Eclipse Gradle tooling cannot import Android projects, the
current focus is the support of Java projects. Android support seems
planned for the 1.0 release,
Am 11.05.15 um 17:55 schrieb Massimo Montecchi:
Please, maintain ADT in a working state for future versions of Eclipse.
see https://github.com/eclipse/andmore and
http://www.vogella.com/tutorials/EclipseGradle/article.html
--
You received this message because you are subscribed to the Google
is a first fix for this. Expect another one sometimes next week.
For new features, our focus is Studio.
On Sun, Jun 29, 2014 at 4:37 AM, Csaba Kozák kozak...@gmail.com
javascript: wrote:
Can we get an official statement about the future of ADT? From the
outside it seems ADT is a little
Please, maintain ADT in a working state for future versions of Eclipse.!!!
Il giorno venerdì 4 luglio 2014 14:15:13 UTC+2, b0b ha scritto:
Eclipse + ADT being slowly abandonned is worrying me.
I'm an happy Eclipse user. I don't want to switch to another IDE.
Eclipse + ADT has been extremely
we get an official statement about the future of ADT? From the outside
it seems ADT is a little-bit abandoned project. It does not get any
improvements, only the most crucial updates to stay compatible with the new
SDKs. With ADT 23, even the compatibility updates were missing
Eclipse + ADT being slowly abandonned is worrying me.
I'm an happy Eclipse user. I don't want to switch to another IDE.
Eclipse + ADT has been extremely reliable for a long time now.
My somewhat complex project builds reasonnably fast with ADT.
I don't even know if I could build it with gradle
On Tuesday, 1 July 2014 02:20:31 UTC+1, Xavier Ducrohet wrote:
For new features, our focus is Studio.
One of the most important features we would like to see if the Eclipse ADT
is support for AAR libraries. Is this still on the cards?
-- @rgladwell
--
You received this message because
On Wednesday, July 2, 2014 6:16:24 PM UTC+2, Mark Murphy (a Commons Guy)
wrote:
On Wed, Jul 2, 2014, at 11:18, Kevin Schultz wrote:
I have never met anyone that has used
IntelliJ extensively but still prefers Eclipse
I do not know how you define extensively, but I definitely have met
On Wed, Jul 2, 2014, at 11:18, Kevin Schultz wrote:
I have never met anyone that has used
IntelliJ extensively but still prefers Eclipse
I do not know how you define extensively, but I definitely have met
people who do not like IntelliJ. There are developers who use NetBeans
too, or no IDE at
From what I can tell, most of the really good teams are using Android
Studio + Gradle or IntelliJ + Maven already.
I think that is a bit early to say. I would say we are a good team, but
we haven't successfully been able to migrate over due to our builds simply
not working in gradle. In
.
On Wednesday, July 2, 2014 11:18:31 AM UTC-4, Kevin Schultz wrote:
I think the future of Eclipse+ADT is pretty clear to anyone following the
development of Android Studio. It is going to be a second class citizen at
best. I honestly hope that it gets killed off completely so as not to pull
From what I can tell, most of the really good teams are using Android
Studio + Gradle or IntelliJ + Maven already.
I think that is a bit early to say. I would say we are a good team, but
we haven't successfully been able to migrate over due to our builds simply
not working in gradle. In
What's going on with your projects? Do you have custom logic in there?
I'm interested in helping you figure out the need to call assemble twice.
On Wed, Jul 2, 2014 at 10:40 AM, Justin Breitfeller mrsl...@gmail.com
wrote:
From what I can tell, most of the really good teams are using Android
Another showstopper to full migration is lack of NDK support with
Studio, specifically NDK Debugging. It is not clear to me what the
migration pattern will be for developers who require NDK debugging.
On 7/2/14, 8:16 AM, Mark Murphy wrote:
On Wed, Jul 2, 2014, at 11:18, Kevin Schultz wrote:
Sorry I am getting this information relayed from one of my coworkers. The
exact error we get is:
error: cannot access NonAcceleratedOverlay
public class MyProjectOverlay extends SomeBaseClass
^
class file for org.osmdroid.views.overlay.NonAcceleratedOverlay not found
On Wednesday, July 2, 2014
Thanks for both of your answers!
I should not have bring the problems of SDK 23 here. It affects the Gradle
build system too, also i was sure that you guys will fix it. Thanks for the
first patch, appreciated!
Xavier is very, very diplomatic, but i guess this means ADT will indeed go
away. I
kozakcs...@gmail.com wrote:
Can we get an official statement about the future of ADT? From the outside
it seems ADT is a little-bit abandoned project. It does not get any
improvements, only the most crucial updates to stay compatible with the new
SDKs. With ADT 23, even the compatibility updates
17 matches
Mail list logo
