[
https://issues.apache.org/jira/browse/CB-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801031#comment-13801031
]
ASF subversion and git services commented on CB-5060:
-----------------------------------------------------
Commit 0596e47f870a13d8658ebb27f01f70fffcec5e23 in branch refs/heads/master
from [~shepheb]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=0596e47 ]
Overhaul dependency uninstallation
This fixes several long-standing bugs with plugman deleting
dependencies. The new rules are to uninstall all of the target plugin's
dependencies, provided they are:
- Not installed at the top level.
- Not depended on by any other plugins.
Similarly, plugin directories are only deleted when no plugin depends on
them, and they are not top-level, on any platform.
Fixes CB-5056, CB-5060, CB-4992, and CB-4189.
> Plugman should not auto-remove installed plugins
> ------------------------------------------------
>
> Key: CB-5060
> URL: https://issues.apache.org/jira/browse/CB-5060
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
> Reporter: Mike Billau
> Fix For: 3.2.0
>
>
> If you install a plugin manually as a top level plugin, but that plugin is
> also used as a dependency for a second plugin, then removing the second
> plugin *should not* remove the first plugin. Currently, this is the behavior:
> {noformat}
> cordova plugin add file
> cordova plugin add file-transfer
> cordova plugin ls
> [file, file-transfer]
> cordova plugin rm file-transfer
> cordova plugin ls
> [ ]
> {noformat}
> If you manually install a plugin, that means you are planning to use it. If
> another plugin depends on it, great, that's fine, whatever, but if you later
> decide not to use the consuming plugin, it shouldn't remove the one that you
> added.
> This is different than the reference counting issue in
> https://issues.apache.org/jira/browse/CB-5056
--
This message was sent by Atlassian JIRA
(v6.1#6144)
