one source for version information is better although parsing json with bash scripts seems janky
On Tue, Aug 12, 2014 at 11:31 AM, Jesse <purplecabb...@gmail.com> wrote: > I think it still needs to exist in an output project ... which is not > (yet?) an npm project, and so does not have a package.json. > > The individual platform repos can get rid of it, they will just need to > modify the way they `create` new projects to read the value from > package.json and output it to NewProject/VERSION > > > > > @purplecabbage > risingj.com > > > On Tue, Aug 12, 2014 at 11:25 AM, Shazron <shaz...@gmail.com> wrote: > > > For iOS, the only file I can see that depends on this is: > > > > 1. > > > https://github.com/apache/cordova-ios/blob/master/bin/templates/scripts/cordova/version > > > > Not sure of the alternative. > > > > This references it but can be removed: > > https://github.com/apache/cordova-ios/blob/master/bin/create > > > > > > On Tue, Aug 12, 2014 at 11:19 AM, Steven Gill <stevengil...@gmail.com> > > wrote: > > > Most of our repos have a package.json. It keeps track of versions. I > > think > > > we should work towards removing the VERSION files from the repos we > can. > > > > > > Thoughts? > > > > > > This would require some changes to coho so it doesn't try to update the > > > version file when doing releases. > > >
