You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Braden Shepherdson (JIRA)" <ji...@apache.org> on 2013/10/21 22:21:49 UTC

[jira] [Resolved] (CB-5060) Plugman should not auto-remove installed plugins

     [ https://issues.apache.org/jira/browse/CB-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Braden Shepherdson resolved CB-5060.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2.0
         Assignee: Braden Shepherdson

> 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
>            Assignee: Braden Shepherdson
>             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)