Bug 123465

Summary: extending "classpath variables" and "linked resources"
Product: [Eclipse Project] JDT Reporter: nicola guidotto <nicola.guidotto>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3    
Version: 3.2   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description nicola guidotto CLA 2006-01-11 12:05:47 EST
Currently the support for variable is usefull, but sometime I'm looking for something like that the variable value can be a variable too, late resolving.
I mean, consider the case where you must have the following variable TOMCAT_5_0 and TOMCAT_5_5, rapresenting your environment, but you configure a set of projects to use a variable named TOMCAT, valued as TOMCAT_5_0. When you need to switch to TOMCAT_5_5 you change only the TOMCAT value in only one place, updating all the project set accordingly.
I use a lot of variable for "relative" resource, and I feel the need of this feature enhancement.

Another refinement I like to find in the "New variable" dialog, may be a text field  where I can optionaly describe the meaning of the cryptic variable names, e.g. M2_REPO stands for MAVEN_2_LOCAL_REPOSITORY.
And obviously, the relative variable list may be optionaly shows a description column too.
This may be applied to "classpath variables", "linked resources" and any other fauture where a variable could be defined and used.

Thanks, in advance.

PS: I apologize for my bad eglish.