Adding <or> makes sense to me, and we may as well throw in <and> at the same time.
I think the default logic should still be AND. Braden On Thu, Nov 14, 2013 at 1:51 PM, Andrew Grieve <[email protected]> wrote: > <and><or>? > > > On Thu, Nov 14, 2013 at 11:44 AM, Braden Shepherdson <[email protected] > >wrote: > > > I think the "AND" logic was chosen because you can specify <engine > > name="cordova-android" version=">=3.2.0" /> or similar, in order to > require > > sufficiently new versions of the platforms. > > > > I agree that only makes sense for platform engines, and makes worklight > vs. > > phonegap vs. cordova engines broken. I don't know how we want to handle > > that. > > > > Braden > > > > > > On Wed, Nov 13, 2013 at 10:08 PM, Qi LUO <[email protected]> wrote: > > > > > Hi all, > > > > > > From the doc, we can specify multiple engines, sth like, > > > > > > <engines> > > > <engine name="cordova" version="1.7.0" /> > > > <engine name="worklight" version="1.0.0" platform="android" > > > scriptSrc="worklight_version"/> > > > </engines> > > > > > > The plugman will only install the plugin after all engines are > satisfied. > > > But I didn’t quite follow the idea that why all engines over there > should > > > pass the check, why not just one of engines? Usually a specific project > > is > > > connected to a specific engine, not two or more. As for plugin, it may > > > support multiple engines, but when it gets installed into a specific > > > project, it’s bound to the only engine used by that project. > > > I didn’t understand the use case in the situation. > > > Thanks. > > > > > > > > > Best Regards, > > > > > > Qi LUO > > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig) > > > > > > > > >
