3.4.1 release exists for only iOS and CLI platforms.js is updated to accordingly so at least it does feel like it is happening. -- Gorkem
On Mon, Apr 7, 2014 at 3:07 PM, Anis KADRI <[email protected]> wrote: > Have we actually decided to move along with the plan? I thought we were > only discussing it. > > > On Mon, Apr 7, 2014 at 2:04 PM, Joe Bowser <[email protected]> wrote: > > > We don't know yet because we're still figuring this out. > > > > On Mon, Apr 7, 2014 at 2:00 PM, Gorkem Ercan <[email protected]> > > wrote: > > > Hi, > > > With the independent platforms releases I have started to run into a > > > problem with my Eclipse tools that I am looking for some suggestions. > > > > > > In the past, Cordova X.Y.Z meant all platforms would be tagged and > > released > > > with X.Y.Z. so if Eclipse tools needed to download Cordova version > X.Y.Z, > > > it could just do so by using the X.Y.Z git tag. Now that platforms can > do > > > independent releases the X.Y.Z tag for may not exist for a release for > a > > > platform. So I actually need a way to determine what platform versions > go > > > together. CLI actually captures that information on platforms.js for > the > > > release but this is not enough for Eclipse tools as it does not capture > > the > > > data for older releases and Eclipse tools can be download and use older > > > versions. > > > > > > Is there a place where I can extract this sort of platform version > > > information? > > > Also in the past, plugins could define engine compatibility as below > > > <engine name="cordova" version="1.7.0" /> > > > How does plugman act with the independent releases now? > > > -- > > > Gorkem > > >
