cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Mocny (JIRA)" <>
Subject [jira] [Commented] (CB-4735) Support optional plugin dependancies
Date Wed, 04 Sep 2013 15:29:51 GMT


Michal Mocny commented on CB-4735:

There are two use cases:

(1) The traditional suggested "add-ons" a la package managers, as you mentioned already. 
They are not installed automatically, just listed for your convenience.  They likely have
low(er) usage counts.
(2) Installed by default, but removable without harm.

Specific example for (2) is Logger plugin for iOS, which we have discussed as always installing
by default, but supporting removal without needing some sort of --force.
Someone on the mailing list also asked for "plugin aliases" which would be a curated list
of plugins to install as dependencies, but could still be removed individually after the fact.

Perhaps another way of looking at it is that we have three category of dependency: required
(the current default), regular (my request with this JIRA), suggested (traditionally supported
by package manager)
> Support optional plugin dependancies
> ------------------------------------
>                 Key: CB-4735
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: CLI, Plugman
>    Affects Versions: 3.0.0
>            Reporter: Michal Mocny
>            Assignee: Braden Shepherdson
> plugins (and perhaps soon apps, and perhaps some future day platforms, too) support plugin
dependencies.  However, right now all dependents are mandatory for the successful use of the
depending plugin.  It would be nice to be able to list optional dependencies which allow for
conditional enhancement, but are not a core requirement.
> One quick example: Logger for iOS would be a nice default dependency of the platform,
but should be safely removeable, and CLI should remember and respect the users decision to
remove it if they chose to.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message