Bug 417175 - Per-resource substitution variables
Summary: Per-resource substitution variables
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 4.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-13 07:23 EDT by Dmitry Stepanov CLA
Modified: 2019-11-27 13:13 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Stepanov CLA 2013-09-13 07:23:50 EDT
I'd like to have a possibility to specify a per-resource string substitution variables (specifically, in "Project Properties", but would be useful if would be supported for any kind of resource), which would automatically become available to all of the run / external tool configurations.

A specific use case:
1) Define an External Tool to the Workspace ("My Tool"). Let's say it's path is "my_tool" and arguments are "--resource-arg=${arg_for_tool}"
2) Create project A, open "Project Properties", click "String Substitution", add a variable "arg_for_tool" with value "A";
3) Create project B, open "Project Properties", click "String Substitution", add a variable "arg_for_tool" with value "B";
4) Create project C and define no string substitution variables for it;
5) Focus any resource inside project A (or project A itself) and run the "My Tool" External Tool. The tool shall invoke "my_tool --resource-arg=A" command;
6) Focus any resource inside project B (or project B itself) and run the "My Tool" External Tool. The tool shall invoke "my_tool --resource-arg=B" command;
7) Focus any resource inside project C (or project B itself) and run the "My Tool" External Tool. You should see the "invalid variable my_tool" error message (or something similar that happens when you misspel a variable name);
8) If you add a workspace-wide string substitution variable "arg_for_tool" with value "W", the step 7 should invoke "my_tool --resource-arg=W" command.

Such feature would be very useful for defining common external tools which behave differently depending on the project being worked on / resource being kept in focus.
Comment 1 Lars Vogel CLA 2019-11-27 07:06:18 EST
This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.
Comment 2 Dmitry Stepanov CLA 2019-11-27 08:08:13 EST
Removed "stalebug" whiteboard tag.

Feature request is still relevant for me.