Return-Path: X-Original-To: apmail-cordova-issues-archive@minotaur.apache.org Delivered-To: apmail-cordova-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0B12810BA0 for ; Mon, 10 Mar 2014 09:10:56 +0000 (UTC) Received: (qmail 29886 invoked by uid 500); 10 Mar 2014 09:10:55 -0000 Delivered-To: apmail-cordova-issues-archive@cordova.apache.org Received: (qmail 29809 invoked by uid 500); 10 Mar 2014 09:10:49 -0000 Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list issues@cordova.apache.org Received: (qmail 29782 invoked by uid 99); 10 Mar 2014 09:10:43 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 09:10:43 +0000 Date: Mon, 10 Mar 2014 09:10:43 +0000 (UTC) From: "SidneyS (JIRA)" To: issues@cordova.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CB-3445) Move Cordova-Android Build Setup to Gradle MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CB-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924126#comment-13924126 ] SidneyS edited comment on CB-3445 at 3/10/14 9:09 AM: ------------------------------------------------------ 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. Also, Android Studio is not needed - 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. was (Author: sidneys): 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 to get company time so that one of our 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)