cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anis KADRI <>
Subject Re: Unifying the config.xml
Date Mon, 01 Apr 2013 19:24:10 GMT
I would like this to be reviewed/merged as well because config.xml
differences are becoming a pain in terms of plugin management.

Android has a /cordova/plugins. iOS had a /cordova/plugins in 2.4 and now
has a /widget/plugins.  BlackBerry 10 has a /widget/plugins and is
following the spec by using "feature" instead of "plugin".

Whatever we decide I would like to have some kind of uniformity across


On Thu, Mar 28, 2013 at 12:05 PM, Gorkem Ercan <>wrote:

> Hi All,
> I am working on a set of plugins for Eclipse that will eventually be part
> of the JBoss IDE. I seem to have similar requirements to cordova-cli and
> noticed that some of the things that are planned for cli is well aligned
> with our plans. So I am hoping to contribute as much as I can.
> We also use W3 widget packaging spec based config.xml as a blanket to
> configure a Cordova App for all platforms. However there are differences on
> the config.xml that each platform consumes compared to the W3 spec and as
> you can imagine a more uniform platform behaviour makes our life a bit
> better. So I have tried to take a shot at unifying the differences between
> platforms and created pull requests for android[1]. iOS[2] and CLI[3]. I
> think with these PRs JIRA[4] for migrating from <plugin> to <feature>
> should be resolved (at least for iOS and Android) and its parent[5] should
> be updated.
> The changes are compatible with the existing config.xmls on iOS and
> Android, I think it will be even possible to mix and match the new syntax
> <feature> with the old ones.
> [1]
> [2]
> [3]
> [4]
> [5]
> --
> Gorkem

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message