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

ASF subversion and git services commented on CB-5397:
-----------------------------------------------------

Commit 806651d674a970a7d22ed9c3132f206d88594f0c in branch refs/heads/master 
from [~agrieve]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=806651d ]

Copy config.xml within copy-www-build-step.sh instead of in Copy Resoruces step

Related to CB-5397.
This will allow users to delete the "Staging" group within a CLI project
without breaking their builds. They may want to do this so that there
isn't any confusion when between staging vs. non-staging when doing a
Quick-Open (Command-Shift-O).


> Add CLI's www/, merges/ and config.xml to Xcode project file
> ------------------------------------------------------------
>
>                 Key: CB-5397
>                 URL: https://issues.apache.org/jira/browse/CB-5397
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI, iOS
>    Affects Versions: 3.1.0
>         Environment: MacOS 10.8.5
> XCode 5.01
>            Reporter: Tom Ernhardt
>            Assignee: Andrew Grieve
>             Fix For: 3.4.0
>
>
> The cordova command line "cordova prepare ios" clobbers user-created source 
> code files/directories without warning
> Steps to reproduce:
> # create a test app
> cordova create test com.test test
> cd test
> cordova platform add ios
> # add a plugin
> cordova plugin add https://github.com/apache/cordova-plugin-device.git
> cordova prepare ios
> Then open the generated Xcode project in Xcode
> Add some source code files
> # Now add a different plugin
> cordova plugin add https://github.com/apache/cordova-plugin-console.git
> # WARNING THIS WILL DELETE YOUR APP'S SOURCE CODE FILES
> cordova prepare ios
> All the source code files and directories that you created in 
>   /platforms/ios/www/
> have just been deleted by the cordova CLI without any warning!



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to