[
https://issues.apache.org/jira/browse/CB-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777924#comment-13777924
]
Braden Shepherdson commented on CB-3216:
----------------------------------------
There is now `cordova platform update` starting with Cordova 3.1.0-rc1 (npm
install [email protected] to get the RC version).
It updates the projects without blowing them away, though it can't necessarily
do everything automatically for you and may output instructions for doing any
remaining pieces of the update manually. In the post-3.0 world, where most of
the Cordova code lives in plugins and the platforms change much less, these
manual steps should be few, usually none.
> cordova-cli project upgrade path
> --------------------------------
>
> Key: CB-3216
> URL: https://issues.apache.org/jira/browse/CB-3216
> Project: Apache Cordova
> Issue Type: Improvement
> Components: CLI
> Affects Versions: 2.6.0, 2.7.0, 2.8.0
> Environment: OSX
> Reporter: Philippe Lang
> Assignee: Braden Shepherdson
> 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
> http://docs.phonegap.com/en/2.6.0/guide_upgrading_index.md.html#Upgrading%20Guides
> 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: http://www.atlassian.com/software/jira
