[
https://issues.apache.org/jira/browse/CB-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282709#comment-14282709
]
Graham Mueller commented on CB-8320:
------------------------------------
Ok, I'll try to spell it out a bit more clearly. Reading back through that, I
don't entirely follow myself. So, the scenario is that we have two projects:
the application and the framework. The framework contains our "standard" set of
plugins that all the applications use, but the application itself may also
specify plugins on top of that. The way that cordova loads plugins in the
webview is via that `cordova_plugins.js` / `config.xml` (not exactly sure
which). We could provide this file from the framework project, with all of its
plugins, but then the projects themselves wouldn't be able to specify their
additional plugins. We could allow the applications to provide the
`cordova_plugins.js`, but then they'd be missing the framework's plugins.
Basically, if the plugin code is in the framework, then how can we make sure
that the application is aware of them, short of manually editing the files to
include the framework plugins. Does that make a bit more sense?
> 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-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
