ENVIRONMENT Host: any linux machine (e.g. Fedora, Ubuntu) Eclipse-plugin: any version, e.g. http://autobuilder.yoctoproject.org/pub/nightly/20121128-1/eclipse-plugin/ TOOLCHAIN/SYSROOT: any version, e.g.: http://autobuilder.yoctoproject.org/pub/nightly/20121128-1/adt_installer-QA/ STEPS TO REPRODUCE 1. Install adt-installer and the Yocto ADT plugin for Eclipse 2. Select File New project WITHOUT configuring the plugin in Preferences 3. Select C Project -> Hello World ANSI C Autotools Project 4. Complete the required fields and press OK (Project name: prj1) EXPECTED OUTCOME: 1. Only one error must be displayed announcing that the Project cannot be created and ACTUAL OUTCOME: 1. After pressing the OK button after the normal Error is displayed additional errors appear (see attached “Screenshot at 2012-11-22 19 20 27” image
Created attachment 971 [details] err screen shot
http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/commit/?id=7b9c957e78e9289a5da52aa5b2ae8fc699017aff
Created attachment 1109 [details] error mesage Reopening sice the error message still isn't clear. Please see the new print screen attached
The eclipse-plugin commit id i have retested is: d18c45e0f5367979f7402380ee123242da2b57d5
After further investigation, I have realized that the problem here is the use of ProcessFailureException when we validate the project name. It seems that in the upstream code, even if this error is thrown and shown, after caching it, the process still continues and somehow manages to hit a point where the project configuration is null, showing a second exception. When using a different type of exception, such as OperationCanceledException, only one error message is shown, but whitout offering the possibility to configure the message shown(except for the details).
Doesn't reproduce anymore on Juno and Kepler.
Created attachment 2095 [details] outcome error
Verified with eclipse Kepler poky: 52b788c6df9201764130ab744bf67b770b24b896 eclipse-poky-kepler: 4a167fd662262ebdaa3cf0d332ac0debb52d7904 Ubuntu 14.04, x86_64 Cheers! Andra N.
This is the best we can achieve to prompt the user with the info on the error by clicking the details due to limitation of underline upstream code