That sounds reasonable. The <engine> tag is a bit weird though, in that the dependency is on cli and not platform version. Combined with CLI semver and platform release unbundling, its a bit hard to reason about. It kinda still works because we have default platform versions pinned to cli versions, but users can explicitly install non-default platform versions if they chose, and plugins may have support for only a subset of platforms..
-Michal On Tue, Sep 30, 2014 at 12:11 PM, Ray Camden <rayca...@adobe.com> wrote: > Ah - never mind. I picked a plugin that didn’t have it specified. I picked > another random one and it *was* shown. > > I’d say that for plugins w/o engine support, the site should still say > something, even if > > Engine Number > Not Specified > > > On 9/30/14, 11:09 AM, "Ray Camden" <rayca...@adobe.com> wrote: > > >Query - why isn¹t <engine> data shown on plugins.cordova.io? That seems > >like crucial data that should be displayed, right? > > > >On 9/30/14, 10:59 AM, "Michal Mocny" <mmo...@chromium.org> wrote: > >> > >>In theory, we should know when plugins depend on a certain minimum > >>platform > >>version, and even have a plugin.xml tag to specify this (<engine>), > >>though > >>its a bit indirect and in practice I'm not sure that the requirements are > >>well specified (many plugins just say >= 3.0.0). > >> > > > >
