cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Kim (JIRA)" <>
Subject [jira] [Commented] (CB-4036) <platform> tag should have a "version" attribute
Date Wed, 14 Aug 2013 00:01:48 GMT


Tim Kim commented on CB-4036:

Hey gang,

So I want to check for platform versions, but I'm noticing we are having a few inconsistent
results from calling the version/scripts.

These are the current return values from the master branch:
android: 3.1.0-dev
ios: dev
blackberry10: 3.0.0
Didn't test windows

I'm thinking we need to make some changes to the platform version scripts so that they are
more in synch. In addition, the 'dev' version also futzes up the version requirement attribute.
Currently, if I see 'dev' in the code, it'll just install it. However, I'm pretty sure that
cli or whatever tool is just going to download the master branch so you'll always have dev
which kinda ruins the point of the version attribute.
> <platform> tag should have a "version" attribute 
> -------------------------------------------------
>                 Key: CB-4036
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Plugman
>            Reporter: Shazron Abdullah
>            Assignee: Filip Maj
> This might be hole that we didn't consider.
> I know implicitly if the plugin supported an "engine" version we support what the engine
supports, but here could be one scenario.
> For example, with iOS 7, a plugin CDVFooBar use this awesome NSWhizBang framework. Fine,
with iOS 7, you have to of course build with the iOS 7 SDK, and you can support iOS 6 with
a Deploy Target build setting.
> It runs on iOS 7 - yay.
> It.. blows up on iOS 6 at runtime, because of course NSWhizBang framework does not exist
on iOS 6.
> Now you say, why don't you do Obj-C runtime checks and weak link the framework? Yes,
the plugin author can do that but a plugin user, by parsing the plugin xml (using a tool,
or optically, whatever) cannot know that the plugin does NOT work on iOS 6 - and even though
it "runs" on iOS 6, it does nothing, which is useless and wastes a lot of time.
> So - my proposal is, to add a *"version"* attribute on the *<platform>* tag. It
should follow the syntax for the <engine> version attribute. 
> What would be the default if the version attribute is not there? Not sure what a reasonable
default is yet.

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