Community
Participate
Working Groups
Build 20020618 I wanted to pass the full path to a particular file to an external tool. Naturally, using the UI, I selected 'Specific resource full path' from the list of variables for the Tool Arguments field. However, when I ran the tool, I found that I was only getting a relative path to the resource. Further investigation revealed that I can get the full path by using the 'Specific resource location' variable instead. The variables should be relabeled so that their function is completely clear. Failing this, there should be more informaiton presented to the user when selecting a variable from the list.
This is redone in the new external tool support. Note: new external tool work is not yet released to the head stream and won't for a while yet.
This bug has not been fixed and should not have been closed.
There are now descriptions in the variables dialog, but there is not variable for the "absolute path in the local file system" for a resource. As well, the variable names are not consistent. For example, workspace_loc refers to the locla file system path of the workspace, but resource_loc is the relative path of a resource. *** This bug has been marked as a duplicate of 19756 ***
