[
https://issues.apache.org/jira/browse/CB-8320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282650#comment-14282650
]
Graham Mueller commented on CB-8320:
------------------------------------
Actually, looking a bit further, we don't fully do that they way I thought. Our
actual plugin code sits in the library project still, but we are running the
`plugin install` scripts still to deploy the JS resources. We probably don't
need to do that though -- the resources could just as easily sit in the
library. However, two thing I'm not sure about -- `config.xml` and
`cordova_plugins.js`. How would we get those deployed to the application? If
all the plugins were just in that library, it would be ok, but since we allow
applications to add additional, one off plugins, they have to have those files
in their own project. Any thoughts on that?
> 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]
