Bug 17324 - External Tools: Poor error handling if target not found
Summary: External Tools: Poor error handling if target not found
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P1 critical (vote)
Target Milestone: 2.0 F2   Edit
Assignee: Ryan Cooper CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 16876 16904 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-05-23 10:58 EDT by Nick Edgar CLA
Modified: 2002-05-28 18:38 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2002-05-23 10:58:33 EDT
Build 20020521

- Create a new external tool using just "notepad" as the target.
- It gives you a warning, but continue anyway.
- Try running it.
- You get an error dialog:
title: Run Tool Problem
message: ExternalToolsAction.runAntProblem
Reason: External tool runner internal error

Problems:
- Title should correspond to action, e.g. "Error Running External Tool".
- Message was not looked up properly.
- Having a missing target should not cause an internal error.
Comment 1 Nick Edgar CLA 2002-05-26 14:17:43 EDT
Should allow simple command name if it's on the system path.
E.g. we should support the same targets as Windows' Start / Run command.

Comment 2 Nick Edgar CLA 2002-05-27 14:48:37 EDT
*** Bug 16876 has been marked as a duplicate of this bug. ***
Comment 3 Nick Edgar CLA 2002-05-27 15:41:57 EDT
*** Bug 16904 has been marked as a duplicate of this bug. ***
Comment 4 Simon Arsenault CLA 2002-05-28 16:39:03 EDT
There is better error handling and therefore, better error message displayed to 
the user. Missing target now shows up with a proper error message.

Please open a new PR for the request to support tool targets which are found on 
the system path (a la Windows' Start > Run command).
Comment 5 Nick Edgar CLA 2002-05-28 18:38:44 EDT
Filed bug 18120 for the system path enhancement.