Hey all,
Plugins need to be versioned to be backward compatible with previous
versions of Cordova. I had a discussion with the PhoneGap:Build team
yesterday and they need to be backward compatible. Ally Ogilvie also
mentioned in separate thread that game developers would also need something
like
That sounds reasonable to me.
How would this be maintained? Would there be some automated process that
keeps that mapping up-to-date?
On Tue, Mar 19, 2013 at 10:59 AM, Anis KADRI anis.ka...@gmail.com wrote:
Hey all,
Plugins need to be versioned to be backward compatible with previous
+1
However, I think we may need a better property/value pair name than
just cordova_version:
plugin_versions. This is because I feel like there is a implicit idea that
this particular plugin will work on a specific version of Cordova, but for
all platforms. Whereas in reality, most of the plugins
However, It's expensive to clone down the
repository just to check if the plugin works or not.
Good point Anis, it would be expensive to clone down a plugin simply to disc
I believe we should store some sort of mapping on our discovery server.
Such as:
{
cordova_version:
I'm a little confused. Would we not specify the plugin version in the
config.xml?? Plugins that get published most certainly need to be
versioned on the discovery server side too of course..
On Tue, Mar 19, 2013 at 1:03 PM, Filip Maj f...@adobe.com wrote:
What Michael says seems to make the most
