cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shazron <>
Subject Re: plugins and engines
Date Wed, 04 Jan 2017 01:15:26 GMT
(almost 3 years old...)

TLDR; we should update the engine tags, with as much granularity as

I think we didn't do this because we don't actually know if it *doesn't*
work on an older version (since of course we don't test the current version
with older platform version) and didn't want to unnecessarily restrict a
user from installing it.

We planned to pin core plugins to a cordova-lib version but we decided to
use engine tags in plugins:

On Tue, Jan 3, 2017 at 12:26 PM, julio cesar sanchez <
> wrote:

> I have noticed that most of the plugins don't use the engine tags or have
> them set to cordova 3.0.0 or 3.1.0 which are very old.
> As we drop support for old iOS/Android versions when updating cordova-ios
> and cordova-android, what is our policy for iOS/Android versions support in
> plugins?
> Right now people can use the plugins on very old versions of iOS or Android
> despite we don't support them on the platforms, as the plugins engines are
> set to 3.0.0 or 3.1.0 on most of them.
> Should we start updating the engines to newer cordova versions? or even
> fine grain it to cordova-ios/cordova-android versions?
> I have noticed that we even have engines for iOS versions using apple-ios
> on the engine tag
> engine/blob/master/plugin.xml#L35
> (but not sure if this really does something as the plugin can be
> installed/used in older iOS versions and what works or doesn't work is
> controlled in the code)
> Or just say that the old Android/iOS version is not supported by Cordova
> anymore if someone complains about a plugin not working?

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