[ 
https://issues.apache.org/jira/browse/CB-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924126#comment-13924126
 ] 

SidneyS commented on CB-3445:
-----------------------------

Oh, it is! All developers i know already made the switch some time ago - even 
in large, mission-critical projects (B2B/B2C). Still having Eclipse as the 
expected IDE and thus the enclosed container poses a deterrence to "serious" 
native Developers - its just not helping Cordova at all, and I've been managing 
& fighting for large (300-500 mandays) Cordova projects in our company since 
day 1 ;-)

Also, Android Studio is not needed at all - the gradle build system is 
independent from Android Studio, and as modular wrapper version, it does not 
have any dependencies at all. Actually, it fits the Cordova CLI philosophy 
better than the current setup.

I will try tasking one of our companies' Senior Android & JS Devs (currently 
making his first AngularJS footsteps in one of our Cordova based projects) with 
a test migration to gradle, if thats OK. Cordova would then just include the 
latest stable gradle wrapper for building.

> Move Cordova-Android Build Setup to Gradle
> ------------------------------------------
>
>                 Key: CB-3445
>                 URL: https://issues.apache.org/jira/browse/CB-3445
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Android
>            Reporter: Joe Bowser
>            Priority: Minor
>
> Currently we're using ant for our setup, and our setup can break every time 
> that the Android SDK updates and change its build.xml.  However, the Android 
> Team has created Gradle to be more robust such that it doesn't have the same 
> problems as ant-based scripts.
> This also has the advantage of using Android Studio for development instead 
> of Eclipse, and the ability for us to bundle resources, which is something we 
> haven't been able to do before.
> Moving to Gradle has numerous advantages, but will break scripts, so this is 
> to be moved in the post-3.0 timeframe.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to