One disadvantage of this is that it means plugin dependencies aren't necessarily tested by most cordova developers.
The BlackBerry 10 default plugin system includes a couple of dependencies, and plugin management has had a tendency to be fairly fragile/broken. I'm not opposed to going this way, but if we do, then I'd request that there be a dummy plugin with a dependency (actually, probably with a grand-dependent too) just for the purposes of ensuring that default testing covers these cases. > -----Original Message----- > From: Alexander Sorokin (Akvelon) [mailto:v-als...@microsoft.com] > Sent: Wednesday, March 18, 2015 7:54 AM > To: dev@cordova.apache.org > Subject: (Mobile spec) Replace dependency plugin with plugin list parameter > in createmobilespec > > Hi guys, > > I would like to introduce a little improvement for mobile spec. > > Currently createmobilespec uses dependency plugin to specify the list of > plugins to install. This approach has some limitations, for example after the > app is created the user cannot remove particular plugin because they all are > listed as dependencies of dependency plugin. > > Developers may want to add custom plugin(s) to mobile spec for testing. Also > some plugins could not be supported under particular platform and should > not be installed. > > I've replaced dependency plugin with new command line parameter for > createmobilespec to specify plugin list through CLI. If the parameter is not > passed, createmobilespec will use default list of plugins. > > This change would affect anyone who uses dependency plugin, though, so I > ask a community to review my PR: > https://github.com/apache/cordova-mobile-spec/pull/123/files > > Thanks, > Alexander Sorokin
smime.p7s
Description: S/MIME cryptographic signature
