I don't really think we need this feature: (1) We already have plugin's which support dependencies. Combined with the plugin repository, this means your alias feature is equivalent to creating a do-nothing plugin that specifies its dependencies.
(2) Also, we will soon have a way to specify application template (ie, replace "hello world"), which combined with plugin dependencies for apps, means that creating mobile spec will be as easy as `cordova create PATH_TO_MOBILE_SPEC` and adding platforms. -Michal On Mon, Sep 2, 2013 at 9:40 PM, lmnbeyond <lmnbey...@gmail.com> wrote: > + 1 It's great > > Best Regards! > > > > On 2013-9-3, at 上午8:37, Brian LeRoux <b...@brian.io> wrote: > > > love this idea > > > > > > On Sat, Aug 31, 2013 at 2:36 PM, Jonathan Bond-Caron < > > jbo...@gdesolutions.com> wrote: > > > >> Setting up the mobile spec app was tedious since I didn't know the > >> dependencies. > >> > >> I wrote a small patch that allows to pull a plugin from a git > subdirectory > >> e.g. cordova plugin add > >> https://github.com/jbondc/cordova-labs?subdir=cordova-deps-mobile-spec > >> https://issues.apache.org/jira/browse/CB-4715 > >> > >> It got me thinking there might an opportunity to make this less tedious > >> with an 'alias' > >> > >> e.g. cordova plugin add @cordova-test > >> > >> The @ symbol signals an 'alias' (cordova-test) that cli would expand to > >> "https://.../cordova-plugin-battery-status https:// > .../cordova-plugin-device > >> etc..." > >> The list of plugins simply gets passed to plugman. > >> > >> A couple of 'core' aliases could make it easier to get started with > >> cordova, e.g. > >> cordova plugin add @cordova-common > >> cordova plugin add @cordova-test > >> cordova plugin rm @cordova-test > >> > >> Could also be called packaged / collection / grouped plugins. > >> > >> Thoughts? > >> > >> > >
