What Jake said.
On Fri, Aug 1, 2014 at 2:11 PM, Jake Wharton <jakewhar...@gmail.com> wrote: > Er, *0.13 > > > On Fri, Aug 1, 2014 at 2:11 PM, Jake Wharton <jakewhar...@gmail.com> > wrote: > >> Feature-wise, Gradle 2.0 is no different than what a 1.13 would have >> been. It was just an opportunity to drop all of the deprecated cruft >> accrued over the last two years of the 1.x series. >> >> AOSP "master" is using Gradle 2.0 (where master == idea133 or whatever >> branch development happens on) so it will likely be supported in the next >> minor version of the plugin (e.g., 1.13, most likely). >> >> >> On Mon, Jul 28, 2014 at 7:00 PM, Zac Bowling <z...@apportable.com> wrote: >> >>> Is there an estimated timeline around moving everything to run on Gradle >>> 2.0? I know it's still pretty new but I wondering how much it affects the >>> Android plugin. I noticed a few things were depreciated from the API in >>> Gradle that I was using myself but otherwise my non-Android plugin >>> dependent gradle scripts have made the update easy enough. I'm wondering if >>> I should backport my code to work on 1.12 or just wait until the Android >>> plugin supports 2.0. Right now I'm developing a gradle plugin to use >>> Apportable's alternative NDK and we plan to ship publicly in the next >>> quarter. >>> >>> To give you some background on my project, in our current SDK, we have >>> our own custom built build system for making APKs that is a full >>> replacement for ANT and the NDK makefiles (we call the android tools when >>> need on our own). We had to stop using ANT and the NDK makefiles 3 years >>> ago because we were too limited in what we could do and in our ability to >>> extend everything. Our current build system is python based and was >>> originally based on a forked version of scons but now sits on ninja (to >>> compile and make things fast). It also calls Xcode to build xcode projects >>> for shared code with iOS. >>> >>> We are currently working on a new product that will provide some huge >>> advantages for Android devs over the Google NDK. Unlike our current >>> product, it's mostly targeted at Android native devs that are trying to >>> share code with other platforms and smooth out the headaches and burdens of >>> maintaing cross platform native code and not be entirely focused on at iOS >>> devs porting to Android from iOS like our current product. As part of that, >>> we were debating on refactoring our current build system but we came to >>> conclusion that we shouldn't break the UX flow of how you build Java for >>> Android (it's only the native side which is what were are trying to >>> improve). The new build system with Gradle opened some doors for us to make >>> this happen (thank you to whomever at Google had the idea to switch off >>> ANT). >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "adt-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to adt-dev+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to adt-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
