cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Maj (JIRA)" <>
Subject [jira] [Resolved] (CB-3216) cordova-cli project upgrade guide
Date Mon, 03 Jun 2013 22:24:23 GMT


Filip Maj resolved CB-3216.

    Resolution: Won't Fix

Unfortunately we will not be tackling this problem anytime soon.

For now, the upgrade path is to upgrade your cordova cli tools and recreate a project.

Re-adding plugins and whatnot should not be a big hassle, though. Just re-run the commands
to add the appropriate plugins to your project.

Please note that upgrading your cordova cli tools means you will be using a new version of
the cordova framework. If you want to stick to cordova 2.5, then stick with the cordova cli
tools from 2.5.
> cordova-cli project upgrade guide
> ---------------------------------
>                 Key: CB-3216
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: CLI
>    Affects Versions: 2.6.0
>         Environment: OSX
>            Reporter: Philippe Lang
>            Assignee: Filip Maj
>              Labels: cordova-cli, platform, update
> Hi,
> I wanted to upgrade an cordova-cli 2.5 generated project tree (with ios and android platforms)
to the latest cordova-cli 2.6 version.
> I somehow managed to do this by reading
after upgrading my npm cordova package ("npm -g update cordova"), but file paths and a few
details are not 100% identical, and I end up being not sure I did everything correctly. (Although
both patforms compile correctly)
> Is there some kind of upgrade guide somewhere, that explains this task? In my case, it's
hard do delete both platforms and recreate them, since boths contain native plugins. But if
it's the way to go, it is not such a big deal eiter...
> A "cordova platform update ios" or "cordova platform update android" would be great.
Any chance we can have that one day?
> Best regards,
> Philippe

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message