[
https://issues.apache.org/jira/browse/CB-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677359#comment-13677359
]
Frederico Costa Galvão commented on CB-3216:
--------------------------------------------
If there is no change in the native "shell" of the application, there is almost
nothing to do other than copy files around www's. As that's not true for most
of us, I've found a good enough way to upgrade my apps.
I haven't used cordova-cli to upgrade anything yet on my cordova project, but
I've used the same procedure to upgrading since october 2012:
I maintain empty(created and not modified) projects of each cordova version
I've used/plan on using. When a new version is released, I create an empty
project from ./bin/create and compare with the one created on the version I'm
currently using, understand the changes (which are always on
AndroidManifest.xml, config.xml, <APP>.java essentialy. You could look for
changes in the main htmls and css for tips on improvements, but that's
optional) and apply those changes to my real project.
On Android, those changes were never more than a line or two
changed/removed/added on config.xml/AndroidManifest.xml. On iOS changes on
.plist and such were a little more verbose and hard to deeply understand, but
never brought any issues either.
IMO the main problem when upgrading to a newer cordova version are plugins
compatibility and big breaks (like localStorage and 9-patch). And I hope
plugman, along with separating each plugin into its own repository and the new
plugin handling coming in 3.0 change that for good.
> 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: 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
> 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
