Make that CB-2448 <https://issues.apache.org/jira/browse/CB-2448>.
On Mon, Jul 8, 2013 at 9:49 PM, Andrew Grieve <agri...@chromium.org> wrote: > Yes! Most of us here have hit that exact problem, but I guess it hadn't > made it to the ML yet. > > It's because Android's version script reports the version by parsing it > out of the comment in the cordova.js file. > > This is completely wrong, since it's not even reporting the version of the > Android repo, but rather the version of the cordova-js version. > > You can work around it by editing the comment in the .js file, or just > having the version script echo a newer version. > > > How I think we should fix this problem is by: > 1. Have the version script hardcode the version within it (or just convert > it to a VERSION file) > 2. Have the create script generate the version script by reading the > VERSION file. If it says "dev", then use git describe to generate the > version > 3. Address CB-3216 so that the version script will be replaced with new > versions on upgrades. > > > > On Mon, Jul 8, 2013 at 6:33 PM, Filip Maj <f...@adobe.com> wrote: > >> I am going to look into this but you shouldn't have to run the cli, you >> can run plugman instead but I am not sure if that¹s the answer you are >> looking for joe ;) >> >> On 7/8/13 2:07 PM, "Joe Bowser" <bows...@gmail.com> wrote: >> >> >Hey >> > >> >I was looking for a quick way to add all the plugins, so I decided to >> >follow the "WorkingWithThree" wiki to set up a 3.0.0 Cordova project. >> >I got most of the way through the guide but ran into an error after >> >running this: >> > >> >../cordova-cli/bin/cordova plugin add >> >../cordova-mobile-spec/dependencies-plugin >> > >> >This is the error I got: >> > >> >[TypeError: Invalid Version: 2.7.0rc1] >> > >> >Any idea why this would happen? Does this have something to do with >> >how we get the version when we run git describe? It looks like I'm >> >going to have to install all the plugins manually or write my own >> >script. >> > >> >Side Note: It'd be great if we didn't have to rely on the CLI to do >> >everything, so that we're not totally SOL if/when we find issues with >> >the CLI. >> >> >
