[
https://issues.apache.org/jira/browse/CB-9248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605895#comment-14605895
]
Nikhil Khandelwal commented on CB-9248:
---------------------------------------
Cordova just does not support the notion of adding a plugin to only part of the
platforms currently.
Perhaps in this case, the plugin should be fixed to not fail for some platforms
at build time.
We had another feature in mind earlier is that if a plugin does not supported
for a platform then it would not end up defining the corresponding elements for
that platform at runtime and hence, allow for feature detection. Would that
help your scenario? Can you share your use case and the specific plugin that
causes problems?
> In config.xml, <plugin> inside <platform> is not supported
> -----------------------------------------------------------
>
> Key: CB-9248
> URL: https://issues.apache.org/jira/browse/CB-9248
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI, CordovaLib
> Affects Versions: 5.1.2
> Reporter: Leroy van Engelen
> Assignee: Rob Paveza
>
> In config.xml it is possible to define plugins that should be installed using
> the <plugin> tag. Some plugins are not available or are buggy on certain
> platforms. Therefore we need to include them depending on the platform. I
> would expect this to be possible by wrapping them in <platform> tags, but
> these are ignored.
> The problem is that in `cordova-lib/src/configparser/ConfigParser.js` the
> methods `getPluginIdList` and `getPlugin` only top level <plugin> definitions
> are taken into account.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
