You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/08/14 00:12:47 UTC
[jira] [Commented] (CB-4490) version check should check
against plugman version
[ https://issues.apache.org/jira/browse/CB-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738909#comment-13738909 ]
ASF subversion and git services commented on CB-4490:
-----------------------------------------------------
Commit 7215cf3ac11bea47bcc354d6f9d2cd89cb9942f9 in branch refs/heads/engineCheck from [~timkim]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=7215cf3 ]
[CB-4490 & CB-4036] - added check for cordova-plugman and made a util function
> <engine> version check should check against plugman version
> -----------------------------------------------------------
>
> Key: CB-4490
> URL: https://issues.apache.org/jira/browse/CB-4490
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugman
> Reporter: Andrew Grieve
> Assignee: Filip Maj
>
> Currently, we have:
> <engine name="cordova" version=">=1.7.0" />
> This checks against the result of platform/bin/version scripts. However, it's quite possible to have a plugin that works with cordova-android >=3.0 and cordova-ios >=3.1
> CB-4036 introduces per-platform SDK & OS version checks.
> This issue covers have cordova versions be per-platform, as well as having plugman version requirement.
> <engines>
> <engine name="cordova-plugman" version=">=3.0.0" />
> <engine name="cordova-android" version=">=3.0.0" />
> <engine name="cordova-ios" version=">=3.1.0" />
> </engines>
> We could still maintain:
> <engines>
> <engine name="cordova" version=">=3.1.0" />
> </engines>
> as a shorthand for:
> <engines>
> <engine name="cordova-plugman" version=">=3.1.0" />
> <engine name="cordova-android" version=">=3.1.0" />
> <engine name="cordova-ios" version=">=3.1.0" />
> </engines>
--
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