You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Andrew Grieve (JIRA)" <ji...@apache.org> on 2014/01/15 15:41:21 UTC
[jira] [Resolved] (CB-5777) Upgrading project from cordova 3.2.0 to
3.3.0 did not update cordova.js in all locations
[ https://issues.apache.org/jira/browse/CB-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Grieve resolved CB-5777.
-------------------------------
Resolution: Fixed
Yikes - thanks for figuring this out Adam!
Fix will go out in 3.3.1-0.2.0 (today hopefully)
> Upgrading project from cordova 3.2.0 to 3.3.0 did not update cordova.js in all locations
> ----------------------------------------------------------------------------------------
>
> Key: CB-5777
> URL: https://issues.apache.org/jira/browse/CB-5777
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.3.0
> Reporter: Adam George
> Assignee: Andrew Grieve
>
> I tried updating my cordova project today to 3.3.0.
> I followed the instructions here:
> http://cordova.apache.org/docs/en/3.3.0/guide_cli_index.md.html#The%20Command-Line%20Interface_updating_cordova_and_your_project
> This did not update cordova.js in all the locations in my project. For iOS projects, cordova.js lives in three separate locations:
> 1. /platforms/ios/CordovaLib/cordova.js
> 2. /platforms/ios/www/cordova.js
> 3. /platforms/ios/platform_www/cordova.js
> When I upgraded my project, only cordova.js in locations 1 & 2 were updated. 3. was not.
> Unfortunately, that meant next time I built my project with `cordova build ios`, the cordova.js in location '2' was clobbered with the version from location '3'.
> The same thing appears to happen on Android too.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)