[
https://issues.apache.org/jira/browse/CB-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789326#comment-13789326
]
Mike Billau commented on CB-4189:
---------------------------------
I'm pretty sure the fact that we don't know the difference between an
explicitly installed plugin and one installed as a dependency is causing this
bug and this (possibly duplicate) one:
https://issues.apache.org/jira/browse/CB-5016.
FWIW I agree with Braden that in Andrew's case, the second ls should only show
console, since the file plugin was installed implicitly as a dependent plugin.
> 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 was sent by Atlassian JIRA
(v6.1#6144)
