Community
Participate
Working Groups
Build F2 When trying to run a shell script using External tools, the error messages for common errors could be improved. If the script does not have the executable bit set, then the error that is reported is: External tool failed to run because of an internal error. Reason: ${tool-path}: cannot execute If the script is missing the appropriate #! ${command} declaration at the beginning of the file, the error reported in the log console is: Warning: UNIXProcess.forkAndExec native error: Exec format error If the script contains the wrong path in the #! ${command} declaration, then the error reported to the log console is: Warning: UNIXProcess.forkAndExec native error: No such file or directory It would be better if the user could be told exactly what is wrong in each case.
I agree, we should continue to improve our error messages. But sometimes it is not possible given the message given in the Exception we catch. We need to verify that the exception does not have a better message than what we are displaying. Or maybe it contains another exception with a better error message. Otherwise, the only option left is to look for these "common" error condition when the exception is thrown and try to generate a better message. This may be tricky because it would be platform dependent (windows does not have an execute permission flag problem, for example).
marking as later - nothing planned for 2.1
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
