Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 14 Oct 2016 22:17:21 +0000 (UTC)
From: "Joe Bowser (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.12967159.1462905401000.836463.1476483441523@Atlassian.JIRA>
In-Reply-To: <JIRA.12967159.1462905401000@Atlassian.JIRA>
References: <JIRA.12967159.1462905401000@Atlassian.JIRA> <JIRA.12967159.1462905401199@arcas>
Subject: [jira] [Commented] (CB-11244) Update Android Project Structure to
 be more compatible with Android Studio
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 14 Oct 2016 22:17:23 -0000


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

Joe Bowser commented on CB-11244:
---------------------------------

[~stickbyatlas] That's probably never going to entirely go away, and it's a consequence of us not releasing as fast as Google releases Android Studio.  We did sync our versions and remove that error for 2.1, but it came back for 2.2 and the next major version will have that fix.  We try to keep up, but our ability to release as fast as possible is hindered by factors beyond my control alone.

> Update Android Project Structure to be more compatible with Android Studio
> --------------------------------------------------------------------------
>
>                 Key: CB-11244
>                 URL: https://issues.apache.org/jira/browse/CB-11244
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Android
>            Reporter: Joe Bowser
>            Assignee: Joe Bowser
>              Labels: CordovaAndroidSix
>
> Currently our existing Android projects have the old Android Project structure created by default, even for new projects, which makes no sense since we no longer support Eclipse as the default project editor and have moved to Android Studio for Android development.
> The main reason for doing this is to clean up dependencies and to allow for projects and dependencies to work more like how modern Android projects work and to remove as much custom Gradle code as possible.  This would also allow us in the future to move towards having Android Plugin code work as Android Libraries with Resources instead of just copying things across, which gives us the ability to add JUnit tests and bundled resources.  This would dramatically increase the quality of plugins such as InAppBrowser, and third party plugins such as the Barcode Scanner.
> This would have to be done on the next major version, and the upgrade would be tricky to do.  However, the benefits at this point would greatly outweigh the costs of maintaining the old project structure.  The old cordova-common code in Cordova-Android 5.0.x would allow for plugins in the short term to work with both projects until we get the new project structure ready.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org