[
https://issues.apache.org/jira/browse/CB-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757845#comment-13757845
]
Braden Shepherdson commented on CB-4735:
----------------------------------------
I'm not clear what workflow you're imagining here. The usual approach to
optional dependencies that I've seen, for example in Arch Linux's pacman and
Ubuntu et al's APT is, after installing a package (and its mandatory
dependencies), to list optional dependencies and what adding them gives you,
and maybe whether they're already installed, something like:
Optional dependencies:
BarcodeScanner - Scan barcodes for the child app
Geolocation - Attach location to your posts
These would be set in the <dependency> tag, I suggest, with <dependency
url="..." ... optional="Scan barcodes for the child app" />
> Support optional plugin dependancies
> ------------------------------------
>
> Key: CB-4735
> URL: https://issues.apache.org/jira/browse/CB-4735
> 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: http://www.atlassian.com/software/jira
