cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CB-3846) Upgrading to lazyload version of library breaks under certain conditions
Date Thu, 20 Jun 2013 18:36:20 GMT


ASF subversion and git services commented on CB-3846:

Commit 262a2f9c91e2baf3cc59fb1d26ad235d3cf4fa8c in branch refs/heads/master2 from Fil Maj
[;h=262a2f9 ]

2.8.25. Fixes [CB-3846]: make sure to lazy load libraries whenever prepare is called, as well
as platform. Added a helper lazy_load.based_on_config method that looks into .cordova/config.json
and lazy loads appropriate stock or custom libraries.

> Upgrading to lazyload version of library breaks under certain conditions
> ------------------------------------------------------------------------
>                 Key: CB-3846
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 2.8.0
>         Environment: Mac OS X 10.8.4
>            Reporter: Joe Reda
>            Assignee: Filip Maj
>             Fix For: 3.0.0
>         Attachments: cordova.log, npminstall.log
> I tried to upgrade my version of Cordova to 2.8.19 using npm using the following command,
"sudo npm install -g cordova".  This appeared to work but it resulted in an incomplete install.
 When I try to build my application I get an error-> cp: no such file or directory: /Users/Joe/.cordova/lib/ios/cordova/2.8.0/CordovaLib/cordova.js
> Which is because /Users/Joe/.cordova/ is empty.
> Reason for this is that on running {{build}}, the tools look to the lazy load directory
to retrieve JS and possibly other bits. Currently, lazy load only fires by hooking into {{platform
add}}. Instead, lazy load should be called into for almost every command relying on libraries:
the platform parsers, and possibly others.

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:

View raw message