Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of braden@google.com designates
 209.85.214.46 as permitted sender)
MIME-Version: 1.0
Sender: braden@google.com
In-Reply-To: <CD64EDB0.19A3D%fil@adobe.com>
References: 
 <CAMk5LL=vTZCvLxr1arC+5aCLqkG7Z0HGOg1sOHr1zSjrbzA0KA@mail.gmail.com>
	<CD64EDB0.19A3D%fil@adobe.com>
Date: Tue, 12 Mar 2013 15:56:47 -0400
Message-ID: 
 <CAMk5LL==uyCHaOV187k9Yhj4BPwTokksDsDEoybTj-ws4SER3Q@mail.gmail.com>
Subject: Re: A word about plugins
From: Braden Shepherdson <braden@chromium.org>
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=bcaec52bf02b8c4bc204d7bfb047

--bcaec52bf02b8c4bc204d7bfb047
Content-Type: text/plain; charset=ISO-8859-1

Well, people keep making this implicit assumption and I have to keep fixing
it to keep my several JS-only plugins working.

The problem with plugman is a higher-level problem. If we want to keep
plugman as a separate tool to support building Cordova apps manually, then
we need a solution to detecting what plugins are installed. I'm not sure
what that approach should be.


On Tue, Mar 12, 2013 at 3:36 PM, Filip Maj <fil@adobe.com> wrote:

> So should we file a plugman issue or is this a bigger problem around what
> committers are doing? I'm confused, it sounds like someone did something
> wrong?
>
> On 3/12/13 2:33 PM, "Braden Shepherdson" <braden@chromium.org> wrote:
>
> >This is a problem for adding and removing plugins in plugman. cordova-cli
> >can use the existence of directories in plugins/ to know what's installed,
> >but plugman can't do that. It currently looks for a <plugin> tag or
> ><config-file> tag, and assumes they exist, which causes errors. So I check
> >whether the tag is defined before trying to read attributes from it.
> >
> >That avoids the error but doesn't solve the problem of knowing what is and
> >isn't installed. Plugman just assumes JS-only plugins are never installed,
> >so they can be double installed, and can't be removed.
> >
> >
> >On Tue, Mar 12, 2013 at 3:24 PM, Brian LeRoux <b@brian.io> wrote:
> >
> >> Hey Braden, is there a specific place this happened?
> >>
> >> On Tue, Mar 12, 2013 at 8:45 AM, Braden Shepherdson
> >><braden@chromium.org>
> >> wrote:
> >> > There are JS-only plugins with no native side. Stop writing code that
> >> > expects there will always be a <config-file> or <plugin> directive in
> >> > plugins.xml
> >> >
> >> > There are native-only plugins with no Javascript, too.
> >> >
> >> > Braden
> >>
>
>

--bcaec52bf02b8c4bc204d7bfb047--