Thanks for the feedback! I don't think we should move files around automatically because it could mess with people's source control.
I think using old versions of CLI with newer projects can't be supported, but we can certainly (and I think have been) supporting using newer versions of CLI with older projects. Searching up until you find a cordova.json (or .cordova) sounds like a good way to find the root. On Mon, Dec 30, 2013 at 5:46 PM, Dick Van den Brink < d_vandenbr...@outlook.com> wrote: > CLI searches for the .cordova folder from the current working directory up > to the root. What will be the new approach? Searching for the cordova.json > and .cordova for compatibility? > > > While I do agree on the change I don't really like the if folder exists or > config exists approach thingy, can't we do something with the upgrade > command to move the files around where we want them and just force the new > way? Not sure if this is an ideal approach.. but yeah… > > > I know this makes it really important to use the right cli version on the > projects but I don't believe a new cli with old project structure or the > old cli with new platform versions work now because of the differences > where Cordova.js is stored for example.. So I don't think that's a real > issue. > > > What do you guys think? Or am I talking nonsense right now? > > > > > > Verzonden met Windows Mail > > > > > > Van: Andrew Grieve > Verzonden: maandag 30 december 2013 22:08 > Aan: dev@cordova.apache.org > > > > > > Proposal: > For CLI projects: > - Use ./cordova.json if it exists, otherwise use .cordova/config.json > - Use ./hooks/* if it exists, otherwise use .cordova/hooks/* > - Change the project template to use ./cordova.json instead of > .cordova/config.json > > > Reasons: > - We want users to put .cordova into source control, so shouldn't hide it > - We didn't make plugins/ and platforms/ hidden, so shouldn't hide > .cordova/ > > > Sound good? If so I'll make an issue and work on this. Since it's holidays, > will wait until next week Tuesday (Jan 7) to proceed. >
