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 <[email protected]> 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" <[email protected]> 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 <[email protected]> wrote: > > > >> Hey Braden, is there a specific place this happened? > >> > >> On Tue, Mar 12, 2013 at 8:45 AM, Braden Shepherdson > >><[email protected]> > >> 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 > >> > >
