incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Maj (JIRA)" <>
Subject [jira] [Commented] (CB-560) Cordova breaking iOS plugins
Date Tue, 24 Apr 2012 09:45:33 GMT


Filip Maj commented on CB-560:

Yeah, sorry about the removal of the various namespaces sans notice. Since 1.6, we have agreed
on a [deprecation policy|] but obviously dropped
the ball on this again.

I have added back in the upper-case {{Cordova}} global in commit [2557ed|;a=commit;h=2557edf0].
Will be more careful about this stuff moving forward.

Related is CB-298, wherein we actually add the deprecation notices.
> Cordova breaking iOS plugins
> ----------------------------
>                 Key: CB-560
>                 URL:
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: CordovaJS
>    Affects Versions: 1.6.1
>         Environment: From!topic/phonegap/2G5OPKV_FdQ
someone apparently tried upgrading from PhoneGap 1.1 to 1.6.
>            Reporter: Chris Brody
>            Assignee: Filip Maj
>             Fix For: 1.7.0
>   Original Estimate: 4h
>  Remaining Estimate: 4h
> From 1.4 to 1.5, the namespace was changed from PhoneGap to Cordova which was breaking
all of the existing plugins. I eventually provided a shim class but it was too late to stop
the pain. Then in Javascript only Cordova was changed to cordova, breaking the iOS plugins
yet again. I noticed in cordova (1.6.0) JS:
> if (!window.PhoneGap) {
>     window.PhoneGap = cordova;
> }
> This should have been done for Cordova like:
> if (!Cordova) {
>  Cordova = cordova;
> }
> Yes we should be deprecating the old namespaces for removal in another major release.
Any API changes made before a major release should be made with a workaround, to be deprecated,
and tested with some plugins before shipping.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message