Bug 19753 - [ExternalTools] *_loc are limited by leading slash
Summary: [ExternalTools] *_loc are limited by leading slash
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Nick Edgar CLA
QA Contact:
URL:
Whiteboard:
Keywords: ui
Depends on:
Blocks:
 
Reported: 2002-06-09 23:48 EDT by Chris McLaren CLA
Modified: 2002-09-18 13:59 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris McLaren CLA 2002-06-09 23:48:41 EDT
*_loc variables such as resource_loc, project_loc, and container_loc seem 
limited in their possible uses because of their leading slash. is the leading 
slash an essential part of the location? bug 18407 highlights a minor issue 
around this.
Comment 1 Simon Arsenault CLA 2002-06-10 10:32:26 EDT
The *_loc variables will generate a complete directory string from the root of 
the disk drive (including drive letter on Window's platform). We can't change 
this.

The "*_path" generate a path relative to the workspace root for use within 
core. It should only be used when calling core API. It is not meant to be used 
for concat. with some directory. The format expected by Core is always with a 
leading slash. This variable would typically be used by Ant script who will 
call Eclipse tasks and need to past the path of a resource to it.

Please reopen if I misunderstood what you wanted.