You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "David Peacock (JIRA)" <ji...@apache.org> on 2013/08/29 01:11:52 UTC

[jira] [Commented] (CB-4606) Adding geolocation plug-in causes Blackberry10 build to fail

    [ https://issues.apache.org/jira/browse/CB-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753003#comment-13753003 ] 

David Peacock commented on CB-4606:
-----------------------------------

This only appears to occur when you have more then 1 plug-in that has a rim-permissions node.  For example you will need both the device plug-in and geolocation plug-in to replicate this.
                
> Adding geolocation plug-in causes Blackberry10 build to fail
> ------------------------------------------------------------
>
>                 Key: CB-4606
>                 URL: https://issues.apache.org/jira/browse/CB-4606
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: BlackBerry, CLI, Plugin Geolocation
>    Affects Versions: 3.0.0
>         Environment: Windows 8
>            Reporter: David Peacock
>            Assignee: Lorin Beer
>
> I created a new Cordova project and added Blackberry10 as a platform.  I ran cordova build and everything was fine.  I then added the geolocation plug-in and tried to build again and received the following error:
> [Error: grafting xml at selector "/widget/rim:permissions" from "C:\SVN\vMobile\
> trunk\platforms\blackberry10\www\config.xml" during config install went bad :(]
> Even more annoying trying to remove the plug-in creates the following error:
> [Error: pruning xml at selector "/widget/rim:permissions" from "C:\SVN\vMobile\t
> runk\platforms\blackberry10\www\config.xml" during config uninstall went bad :(]
> To remove I had to remove the blackberry10 platform, remove the geolocation plug-in then re-add the blackberry10 platform.  The underlying issue however looks to be the same.

--
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