You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Graham Mueller (JIRA)" <ji...@apache.org> on 2015/01/16 23:51:34 UTC
[jira] [Comment Edited] (CB-8320) Cordova Plugin Add Doesn't Work
With Newer Android Project Structure
[ https://issues.apache.org/jira/browse/CB-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280822#comment-14280822 ]
Graham Mueller edited comment on CB-8320 at 1/16/15 10:50 PM:
--------------------------------------------------------------
Perhaps "doesn't work" is the wrong way of putting this. Google (or Gradle/Maven, not sure) has mandated a new project structure. They've allowed existing projects to work, but they no longer recommend doing it this way. Will Cordova be migrating to this newer structure, or will projects being staying with the older pattern? And if new projects do adopt the new structure, will they be incompatible with Cordova?
If not, that's fine -- I'm working on a framework that will just need to adjust accordingly, and I want to know if I should expect this to change.
was (Author: shortstuffsushi):
Perhaps "doesn't work" is the wrong way of putting this. Google (or Gradle/Maven, not sure) has mandated a new project structure. They've allowed existing projects to work, but they no longer recommend doing it this way. Will Cordova be migrating to this newer structure, or will projects being staying with the older pattern? And if new projects do adopt the new structure, will they be incompatible with Cordova?
> Cordova Plugin Add Doesn't Work With Newer Android Project Structure
> --------------------------------------------------------------------
>
> Key: CB-8320
> URL: https://issues.apache.org/jira/browse/CB-8320
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Reporter: Graham Mueller
> Labels: gradle, plugins
>
> We've recently started to use the newer project structure recommended for the [Android Tools|http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Configuring-the-Structure]. The basic idea is
> {code}
> /platforms/android
> /build.gradle
> /settings.gradle
> /etc...
> /cordova
> /CordovaLib
> /APP_NAME
> /build.gradle
> /src
> /main
> /assets
> /res
> /java
> /...
> {code}
> When you try to run {{cordova plugin add ...}}, it assumes you have the assets, res, and src at the root of the Android directory. Is there any way to change this expectation, since the newer projects are kind of expected to be this way? I acknowledge that the Android cmd line tool doesn't do this yet, but you can't expect Google to keep up with their own tools.
--
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