cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Braden Shepherdson <>
Subject Re: [plugman] platform tag with version attribute
Date Mon, 01 Jul 2013 20:29:44 GMT
I think we still want <engine>. We (the Google team) discussed this tag a
while back, since it seemed to be contentless. It shouldn't need to be
changed often, since for most plugins the Cordova API is stable.

But sometimes the Cordova bridge or API changes in a way the plugin depends
on, and that's a Cordova-specific version requirement and has nothing to do
with which iOS or Android version we're running on. For example, when we
added ArrayBuffer binary data support to the bridge on Android and iOS.

Most of the plugins are currently requiring ">= 2.4.0" which was the last
time the bridge changed materially. I suspect they'll soon be requiring ">=
3.0.0". If we maintain backward compatibility in the bridge changes, old
plugins will continue to work. If a plugin does depend on new bridge or API
functionality, it can require a sufficiently new version of Cordova.


On Mon, Jul 1, 2013 at 1:20 PM, Filip Maj <> wrote:

> I like this, allows for fine-grained support.
> Does this proposal essentially EOL the <engine> elements in the plugin
> spec? Is there a case where a plugin manifest would want to specify both
> minimum/maximum cordova version constraints AS WELL AS platform os/sdk
> constraints?
> On 6/28/13 3:42 PM, "Shazron" <> wrote:
> >I like Andrew's suggestion to have min-sdk-version and min-os-version
> >instead (commented in the issue). This could be informational (just a spec
> >change), but eventually we can enforce support.
> >
> >
> >
> >
> >On Thu, Jun 27, 2013 at 5:55 PM, Shazron <> wrote:
> >
> >> A proposal:
> >>

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