]
Gorkem Ercan commented on JBIDE-19719:
--------------------------------------
During import Android SDK is not really needed. It is logged only as a consequence of a
chain of calls that tries to precompile the cordova-android runtime to generate the
cordova.jar.
Hence the "Android SDK location is not defined" exception is always logged but
not shown to the user until it actually becomes a blocker for the user. An error dialog
that opens up the appropriate preference is fired when you try to run the project on
Android device/simulator or export for android native formats.
I think we can completely remove the logging or make it a warning but we should not open a
dialog during import.
EasyImport of MobileHybrid project results in errors - lack of
configured Andriod SDK is written to .log, but it is not communicated to the user via the
UI
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-19719
URL:
https://issues.jboss.org/browse/JBIDE-19719
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: integration-platform
Affects Versions: 4.3.0.Alpha2
Reporter: Len DiMaggio
Assignee: Gorkem Ercan
Attachments: jbosstools-diagnostics-20150427143128.zip,
jbosstools-diagnostics-20150428105107.zip
This issue is related to JBIDE-19716
Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools
4.3.0.alpha2 is exported and then imported from a directory using easy import.
See attached .zip for the error file (logs, etc..)
The error message logged is:
eclipse.core.runtime.CoreException: Android SDK location is not defined