Bug 16866 - [ExternalTools] Extra "Tool Location does not exist" error
Summary: [ExternalTools] Extra "Tool Location does not exist" error
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P1 critical (vote)
Target Milestone: ---   Edit
Assignee: Ryan Cooper CLA
QA Contact:
URL:
Whiteboard:
Keywords: ui
Depends on:
Blocks:
 
Reported: 2002-05-22 11:39 EDT by Adam Schlegel CLA
Modified: 2002-09-18 13:58 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Schlegel CLA 2002-05-22 11:39:43 EDT 
When creating an external tool for an Ant script using the New External Tool 
dialog, if you specify the Tool Location using the Browse Workspace button, the 
dialog always reports "Tool Location does not exist" error, even if the tool 
really is there. This does not stop the tool from being run.
Comment 1 Adam Schlegel CLA 2002-05-22 11:41:16 EDT 
The same behaviour occurs when setting the Working Directory using the Browse 
Workspace button.
Comment 2 Simon Arsenault CLA 2002-05-28 14:45:45 EDT 
Part of the problem was that the "Browse Workspace" button for the tool 
location field was generating the wrong variable format. It now generates 
${workspace_loc:<<resource full path>>} instead of ${workspace_loc}<<resource 
full path>> (which is a valid variable and still supported). Tools entries will 
need to be updated to use the proper variable format. Fix in build > 2002-05-28
Comment 3 Adam Schlegel CLA 2002-06-12 09:42:12 EDT 
Verified using 20020611