Bug 18037 - [ExternalTools] Tool location problems with variables
Summary: [ExternalTools] Tool location problems with variables
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 F2   Edit
Assignee: Nick Edgar CLA
QA Contact:
URL:
Whiteboard:
Keywords: ui
Depends on:
Blocks:
 
Reported: 2002-05-28 09:34 EDT by Marco Mulder CLA
Modified: 2002-09-18 13:58 EDT (History)
0 users

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 Marco Mulder CLA 2002-05-28 09:34:25 EDT 
- Create a new External Tool Builder configuration for a project
- Enter a name
- Select "Browse Workspace" for Tool location
- Select a build.xml file in the project

Problems:
- "Tool location does not exist" warning is given while the location does exists.
- ${project_loc:<projectname>} should be used instead of
${workspace_loc}/<projectname>. The current variable does not work for projects
outside of the workspace location.
Comment 1 Simon Arsenault CLA 2002-05-29 14:04:41 EDT 
In the latest integration build (05/29), this problem has been fixed. It will 
now generate the variable ${workspace_loc:/MyProject/build.xml} and will auto-
expand it to the correct directory where that file exist on your hard drive.