I'm working on a high-level what-not-how sort of document for the whole plugin tools story, and this is something I keep coming back to. It's looking like we'll need to know what plugins are installed and where files have been placed where. This is important for uninstalling and also for updating the iOS project files.
If we do need a manifest of that kind, it should absolutely be a shared format between plugman and cordova-cli. Or perhaps more precisely, for anything dealing at the level of files, cordova-cli should be calling plugman, which would deal with the files and update the manifest. I'm not thrilled about having such metadata, but it's hard to use the filesystem as the source of truth here. Thoughts? Braden On Thu, Mar 14, 2013 at 3:21 AM, Filip Maj <f...@adobe.com> wrote: > On 3/12/13 5:26 PM, "Andrew Grieve" <agri...@chromium.org> wrote: > > >One possible solution: Have JS-only plugins add a <plugin> tag with a name > >but no value. > > Thinking more generally here, as Anis said, the problem here is > dependencies. I think determining how aware plugman needs to be of the > project is important. Pretty sure plugman needs to: > > A) know which plugins are installed > B) able to get a reference to each plugin's config file, to be able to > warn of things like collisions > > Does this sound right? > >
