cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Graham Mueller (JIRA)" <>
Subject [jira] [Commented] (CB-8320) Cordova Plugin Add Doesn't Work With Newer Android Project Structure
Date Fri, 16 Jan 2015 21:04:35 GMT


Graham Mueller commented on CB-8320:

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:
>             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
The basic idea is
> {code}
> /platforms/android
>   /build.gradle
>   /settings.gradle
>   /etc...
>   /cordova
>   /CordovaLib
>     /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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message