Hello Julio,
I think we are just answering different questions, both valid. I was speaking to possibility of maintaining source code that uses different version of Cordova, you addressed the necessity of upgrading from 2.9 to 3.X. I agree with you that the upgrade process is going to be very painful… When I did it I had to increment minor versions doing following all the in-between upgrade instructions from the docs and double-checking nothing died on me in the project in terms of functionality. As for the plugins I just switched to using Cordova cli and everything worked fine since (with the exception of couple quirks that I solved by pretty much just removing/installing the plugins). On Fri, Dec 12, 2014 at 3:09 PM, julio cesar sanchez <[email protected]> wrote: > I have not tried what Ivan said, but as you are on version 2.9.0 I don't > think you can because cordova 2.9.0 wasn't installed on the system, just > downloaded, and there is no direct update from 2.9.X to 3.X.X. > What I did when upgraded from 2.9.1 to 3.6.4 was, I generated the > cordova-3.6.4.jar, deleted cordova-2.9.1.jar from the android project, > added cordova-3.6.4.jar and tested, as 2.9.1 included all the plugins in > the core and cordova 3.X.X didn't include them, I had to install the > plugins I was using with plugman. > So, updating like I mentioned, you can generate the .jar for any cordova > version and just test it, but your project won't be a real cordova project > and you'll need to update everytime like this, and install the plugins > using plugman instead of using the cordova CLI > So, the other choice you have is to create a new project using the CLI, > copy your current html, css and javascript and try. If you were using any > plugin it wont work, so you install the plugins you need using the cordova > CLI and then you will be able to update easily on new cordova updates.
