[
https://issues.apache.org/jira/browse/CB-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799390#comment-13799390
]
Kris Erickson commented on CB-5127:
-----------------------------------
Perhaps some of this information (what exactly prepare does) could be added to
the documentation.
Also maybe add a command or an option to the prepare could be added to
're-install' plugins rather than adding them, since uninstalling and
reinstalling plugins is a bit of a pain since it requires the full git path.
For myself, everything is in my VCS and I have added the source code in
platform to the VCS (initially I assumed that it would be like the asset
directory and updated each prepare and kept it out of VCS). I also assumed
that if the plugin got update it would update source code, but I guess that
also is wrong (do you have to remove and re-add plugins to update them in
general).
I like the new plugin architecture but it is very poorly documented (even
finding the list of plugins is frequently a googling safari and without
www.plugreg.com I would have difficulty finding plugins at all.)
> Detect changes to plugins and reinstall their source on prepare
> ---------------------------------------------------------------
>
> Key: CB-5127
> URL: https://issues.apache.org/jira/browse/CB-5127
> Project: Apache Cordova
> Issue Type: Improvement
> Components: CLI
> Affects Versions: 3.0.0
> Environment: Windows 7, cordova CLI 3.0.4
> Reporter: Kris Erickson
> Assignee: Braden Shepherdson
> Fix For: 3.2.0
>
>
> Running
> cordova prepare android
> copies the javascript portion of the plugin, but not the Java source on
> android (haven't yet tested on IOS). Thus when the project is moved between
> machines the source isn't copied if it isn't retained in the VCS or if the
> user adds a platform after adding a plugin. My suggestion would be to copy
> only if the source isn't there in case the user has changed the plugin.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
