[ https://issues.apache.org/jira/browse/CB-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jcesarmobile closed CB-5127.
----------------------------
Resolution: Won't Fix
Assignee: jcesarmobile
Fix Version/s: (was: 3.6.0)
Plugins aren't supposed to be changed in the Cordova project, if you are using a plugin and
doesn't work as you want, then uninstall it and install a fork with the changes using --save
option on plugin install so the reference is copied and the other machine will use the same
fork.
While plugin development, you can use --link option when installing a local plugin and the
source code changes you make will be propagated to the original source. As it only works with
local plugins, once you are happy with it you will still have to commit those changes to a
git repo so the other machine can pick them too.
> 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: jcesarmobile
>
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org
|