[
https://issues.apache.org/jira/browse/CB-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758124#comment-13758124
]
Braden Shepherdson commented on CB-4189:
----------------------------------------
I disagree, actually. We want to start tracking explicitly installed plugins
vs. ones installed as dependencies, and checking which plugins no longer have
dependents and can be removed. If your project actually requires File then you
should install it explicitly. (Or in the future, list it in your app config.xml
as a dependency.)
> Plugman uninstallPlugin plugin repo removal should work bottom-up: dependency
> leaves first, moving up the dependency chain
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CB-4189
> URL: https://issues.apache.org/jira/browse/CB-4189
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugman
> Affects Versions: 2.9.0, 3.0.0
> Reporter: Filip Maj
> Assignee: Mark Koudritsky
> Priority: Minor
>
> Currently, the plugin-repo-removal code (encapsulated as the
> {{uninstallPlugin}} method) blindly removes dependent plugins recursively. It
> should probably do this in a smarter fashion, similarly to how the
> {{uninstallPlatform}} method checks for any other dependents before
> proceeding with recursive uninstalls.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
