[
https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi...
]
Vlado Pakan commented on JBIDE-14544:
-------------------------------------
Current situation with JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493:
Adnroid Emulator is started but build of android application is failing with this error:
{noformat}
[mergemanifest] Merging AndroidManifest files into one.
[mergemanifest] Manifest merger disabled. Using project manifest only.
[echo] Handling aidl files...
[aidl] No AIDL files to compile.
[echo] ----------
[echo] Handling RenderScript files...
[echo] ----------
[echo] Handling Resources...
[aapt] Generating resource IDs...
[aapt]
/home/vpakan/jbdevstudio710Beta1b/studio/configuration/org.eclipse.osgi/bundles/910/data/proj_gen/cordovatest/android/bin/AndroidManifest.xml:20:
error: No resource identifier found for attribute 'hardwareAccelerated' in package
'android'
[aapt]
/home/vpakan/jbdevstudio710Beta1b/studio/configuration/org.eclipse.osgi/bundles/910/data/proj_gen/cordovatest/android/bin/AndroidManifest.xml:22:
error: No resource identifier found for attribute 'xlargeScreens' in package
'android'
[aapt]
/home/vpakan/jbdevstudio710Beta1b/studio/configuration/org.eclipse.osgi/bundles/910/data/proj_gen/cordovatest/android/bin/AndroidManifest.xml:33:
error: No resource identifier found for attribute 'hardwareAccelerated' in package
'android'
[aapt]
/home/vpakan/jbdevstudio710Beta1b/studio/configuration/org.eclipse.osgi/bundles/910/data/proj_gen/cordovatest/android/bin/AndroidManifest.xml:36:
error: Error: String types not allowed (at 'configChanges' with value
'orientation|keyboardHidden|keyboard|screenSize|locale').
BUILD FAILED
/opt/android-sdks/tools/ant/build.xml:653: The following error occurred while executing
this line:
/opt/android-sdks/tools/ant/build.xml:698: null returned: 1
{noformat}
Same error is displayed to console when trying to build Cordova project exported as Native
Platform Project and also when exporting Cordova project as Mobile application. Problem
seems to be target property in generated project.properties file. This property is set to
android-7 as default but it's not possible to build project with this settings. When
changed to android-16 build runs successfully and application runs on emulator. It should
be set appropriately to version of exported project maybe we should add functionality to
specify target android version somewhere in project or/and in export wizards. WDYT?
Cannot run Cordova project on Android Emulator/Device
-----------------------------------------------------
Key: JBIDE-14544
URL:
https://issues.jboss.org/browse/JBIDE-14544
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.1.0.Beta1
Environment: Fedora 17 32bit
Android 4.1.2
Reporter: Stefan Bunciak
Assignee: Gorkem Ercan
Labels: respin-a
Fix For: 4.1.x, 4.2.x
Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52
AM.png
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
{code}
java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:883)
at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
at
org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
at
org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
at
org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
{code}
--
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