[jbosstools-issues] [JBoss JIRA] (JBIDE-16644) Cordova Plugins are not loaded when they are not supported on certain platforms

Gorkem Ercan (JIRA) issues at jboss.org
Thu Feb 27 12:27:47 EST 2014


     [ https://issues.jboss.org/browse/JBIDE-16644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gorkem Ercan updated JBIDE-16644:
---------------------------------

     Original Estimate: 0 minutes
    Remaining Estimate: 0 minutes
         Fix Version/s: 4.2.x

    
> Cordova Plugins are not loaded when they are not supported on certain platforms
> -------------------------------------------------------------------------------
>
>                 Key: JBIDE-16644
>                 URL: https://issues.jboss.org/browse/JBIDE-16644
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: aerogear-hybrid
>    Affects Versions: 4.1.1.Final
>            Reporter: Vineet Reynolds
>             Fix For: 4.2.x
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I added the [Cordova StatusBar plugin|https://github.com/apache/cordova-plugins/tree/master/statusbar] (supported on iOS and not on Android) to my HMT project. When run this project on an Android emulator, the statusbar plugin is not loaded by the tooling, even though a reference to the plugin is added to the starting page of the app - index.html.
> See the [referenced screenshot|http://www.screencast.com/t/Jq5wZWLI8Ho] as an example.
> This is not the case when using the Cordova CLI. The CLI commands ensure that the JS file for the StatusBar plugin is loaded on Android. While a 404 is not harmful in this case, it is certainly not recommended.
> As a note, we must try and match the Cordova CLI behavior as much as possible, and this is a slight deviation from it - the iOS-specific plugin is referenced in {{android/assets/www/cordova_plugins.js}} in the Android project but is not copied to the {{android/assets/www/plugins}} directory in the project.

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


More information about the jbosstools-issues mailing list