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

Dan Moore commented on CB-3216:
-------------------------------

[~plang] The way I am dealing with the changes I have to make to anything under 
platforms is to create a top level directory called config, and put the files 
there that need to be copied someplace under platforms.  Then I have written 
hooks to copy them to the appropriate location.

I haven't done this for ios yet, but it seems to work for android.
                
> 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