[
https://issues.apache.org/jira/browse/CB-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726184#comment-13726184
]
Maciej Jaros commented on CB-4379:
----------------------------------
I don't understand why adding 4 lines of code to support old syntax is a
problem? Also where is a __single__ place I could watch to get the deprecation
information? I expected things like that would be announced on some official
page (e.g. Cordova/PhoneGap project page) and put in the docs before removing
old syntax. Both seems not to be the case here.
In current situation I would expect the four lines of code would be added (and
maybe removed in 3.1 or 3.2).
In future (as mentioned before) it would be nice to get announcements like that
to as many official channels as possible and be put in docs of a version before
any syntax is removed.
Again, not mean to be rude, but you cannot build business products on an
unstable ground.
> Android PluginManager not loading plugins from config.xml
> ---------------------------------------------------------
>
> Key: CB-4379
> URL: https://issues.apache.org/jira/browse/CB-4379
> 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: http://www.atlassian.com/software/jira
