[
https://issues.apache.org/jira/browse/CB-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280730#comment-14280730
]
Andrew Grieve commented on CB-8320:
-----------------------------------
There's currently no plan to change the directory structure. Android Studio and
gradle both work fine with the existing directory structure, so I'm not sure
there is a need to change it. When I say it works "fine" I mean:
- check out 4.0.x branch of cordova-android
- run cordova platform add path/to/cordova-android
- cordova build android
- then import the non-android-studio project of "platforms/android" into
Android Studio.
> 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: [email protected]
For additional commands, e-mail: [email protected]
