cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bowser (JIRA)" <>
Subject [jira] [Commented] (CB-4379) Android PluginManager not loading plugins from config.xml
Date Thu, 01 Aug 2013 15:35:49 GMT


Joe Bowser commented on CB-4379:

Unlike certain other changes with 3.0, we've actually gone out of our way to alert people
to the new plugin changes, and we actually followed our API deprecation policy.  I've even
written blog posts for talking about this change (now buried on Page 3:, so it's not like we're not trying to communicate our changes

Here's the post that was syndicated from June:

This change has been planned for months, and we're not changing this back.  We also try to
have all our planned deprecation changes on the wiki:
> Android PluginManager not loading plugins from config.xml
> ---------------------------------------------------------
>                 Key: CB-4379
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Docs
>         Environment: Windows 7 x64 (but should not be relevant)
>            Reporter: Maciej Jaros
>            Assignee: Mike Sierra
>            Priority: Critical
> When I try to use BarcodeScanner I keep getting "Class not found".
> After debugging with cordova from master I noticed loadPlugins function doesn't set service/class
values for plugins.
> There seem to be a missing if (around line #130):
> {code:java}
>                 }
>                 else if (strNode.equals("plugin")) {
>                     service = xml.getAttributeValue(null, "name");
>                     pluginClass = xml.getAttributeValue(null, "value");
>                 }
>                 else if (insideFeature && strNode.equals("param")) {
> {code}
> Tested this on Android 4.2 (Nexus 7) and it seem to work fine. At the moment the mentioned
plugin is not working but will add a patch for that today.

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