cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Braden Shepherdson (JIRA)" <>
Subject [jira] [Resolved] (CB-4660) Cordova Android project created using Cordova CLI is not compiling in eclipse.
Date Wed, 04 Sep 2013 17:40:51 GMT


Braden Shepherdson resolved CB-4660.

    Resolution: Cannot Reproduce
      Assignee: Braden Shepherdson  (was: Joe Bowser)

This is working for me. I used to have similar errors because my Eclipse was, by default,
targeting too old an API version. Configure Build Path in Eclipse, Android section, and choose
a recent API (like 17) and it should work fine.
> Cordova Android project created using Cordova CLI is not compiling in eclipse.
> ------------------------------------------------------------------------------
>                 Key: CB-4660
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI, Docs
>    Affects Versions: 3.0.0
>         Environment: Window 7, eclipse Juno, Android 2.3 - 4.3
>            Reporter: Venkata Kiran
>            Assignee: Braden Shepherdson
>            Priority: Minor
> When an Android project is created using cordova command line and then imported into
eclipse, the blank project created is not compiling. 
> The following errors are shown during compilation.
> error: Error: String types not allowed (at 'configChanges' with value 'orientation|keyboardHidden|keyboard|screenSize|locale').
> error: No resource identifier found for attribute 'hardwareAccelerated' in package 'android'
> After changing the project target build to 18 from 10, then these errors are resolved,
but the below errors continue even before changing the API version and also the API version.
> DroidGap cannot be resolved to a type
> Config cannot be resolved
> The import org.apache.cordova cannot be resolved
> The method onCreate(Bundle) of type HelloCordova must override or implement a supertype
> The blank project created by cordova should compile without any issues.

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