cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John M. Wargo (JIRA)" <>
Subject [jira] [Commented] (CB-3568) Path problem with Android SDK installation
Date Tue, 04 Jun 2013 15:33:20 GMT


John M. Wargo commented on CB-3568:

OK, it was node version - I upgraded to 0.10.9 and the android platform add worked.  Doing
the same for BlackBerry generates the following:

jmw-mini:test jwargo$ cordova platform add blackberry
[Error: An error occured during creation of blackberry sub-project. Project creation failed!
Error: Error: ENOENT, no such file or directory '/Users/jwargo/dev/cordova-book/test/platforms/blackberry/cordova/node_modules/plugman/main.js'

It creates the platform folder structure and project files, but the BlackBerry merges folder
doesn't get created.
> Path problem with Android SDK installation
> ------------------------------------------
>                 Key: CB-3568
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 2.7.0
>         Environment: Mac OS X
>            Reporter: John M. Wargo
>            Assignee: Filip Maj
> I downloaded the android sdk and extracted it to my downloads folder then added the platform-tools
and tools folders to the path environment. When I create a project and issue a cordova platform
add android, a bunch of stuff happens then eventually I receive an error message indicating
that the process couldn't find the build.xml, but it's looking for the file in /Applications/android-sdk-macosx/tools/ant/build.xml
which is not where my files are located.
> It looks like the cordova cli is forcing an absolute path for the Android SDK - looking
for it in Applications instead of where I have it. The Android SDK instructions for Max OSX
don't say to copy the files to Applications nor does the readme for the Cordova CLI in 2.7.
> I have a screen shot of this, couldn't find the output anywhere that I could past in

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