Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of iclelland@google.com
 designates 209.85.214.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CDFB4E85.21BA8%fil@adobe.com>
References: 
 <CAK_TSX+BV6ZAWsfCs_bY4BgdekjcanmrG_xh6bZH2ziy73i_pQ@mail.gmail.com>
 <CDFB4E85.21BA8%fil@adobe.com>
From: Ian Clelland <iclelland@google.com>
Date: Thu, 4 Jul 2013 23:21:00 -0400
Message-ID: 
 <CAK_TSXJo5z5xFGarFqoXX7N2Y9XB=SHf929LQFrZZEmSm2j-9w@mail.gmail.com>
Subject: Re: Uninstallation of dependency-only plugins
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2570e45cf8404e0bb3007

--001a11c2570e45cf8404e0bb3007
Content-Type: text/plain; charset=UTF-8

Thanks, Fil,

Created CB-4077 to track this. I'll start working on separating those
functions.

Ian

On Thu, Jul 4, 2013 at 7:08 PM, Filip Maj <fil@adobe.com> wrote:

> File an issue over at issues.cordova.io, tag plugman, and we can go from
> there
>
> On 7/4/13 12:59 PM, "Ian Clelland" <iclelland@google.com> wrote:
>
> >This is the first time I've tried to use the CLI tools with the new 3.0
> >project structure, and I've discovered that I can't uninstall a plugin
> >that
> >only has dependencies (no source files, either JS or native)
> >
> >Specifically, I've built a mobilespec app, installing
> >the mobile-spec-dependencies plugin, which does nothing but depend on
> >every
> >Cordova core plugin. I want to remove it, so that I can remove and
> >reinstall one of the dependencies, but the CLI tools will not remove it.
> >
> >Digging through cordova-cli, it looks like "cordova plugin rm" attempts to
> >invoke plugman.uninstall once per platform, but mobile-spec-dependencies
> >doesn't declare any platforms.
> >
> >plugman.uninstall seems to do two things, which I think should be
> >separated: It removes the plugin from a specific platform, and it removes
> >the plugin from the project itself.
> >
> >In the case of a dependency-only plugin, we only need to do the second
> >task
> >(which currently doesn't get done). For a regular plugin which is
> >installed
> >in multiple platforms, this also fails, since removing the plugin for the
> >first platform deletes the plugin source directory, and then removal for
> >subsequent platforms fails with the error message "[Error: Plugin <plugin
> >id> not found. Already uninstalled?]"
> >
> >Can anyone explain the technical reasons behind this, or should I work on
> >separating those functions?
>
>

--001a11c2570e45cf8404e0bb3007--