[ 
https://issues.apache.org/jira/browse/CB-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675687#comment-13675687
 ] 

Filip Maj commented on CB-3216:
-------------------------------

I'm not sure how the cordova-cli tooling is supposed to keep track of arbitrary 
bit changes you make to the native build artifacts (anything under the 
platforms/ directory). Doesn't version control solve that problem?

Essentially, until those types of changes can be abstracted away into the 
config.xml (the icons + splash screens is a good example, which is why we have 
outstanding issues like CB-3301 to solve this), you should be versioning the 
native projects that cordova-cli creates anyways.

Like I said above, this is not a simple problem to solve, and it depends how 
far you want to solve the problem for the users. If you have ideas or 
prototypes on how to solve this issue, the cordova community would love any 
help and contributions to make this happen.
                
> 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

Reply via email to