Description Neale Upstone 2005-05-17 10:03:26 EDT

Something very odd going on here.  At first seems like just a variable not
getting expanded, but then finding that the running app doesn't even get changed
VM args when I change them in the Run Configuration.

Classic situation: want to specify a -D option to tell logging where to get
properties file.

The following demonstrates the situation.  ${project_loc} gets expanded in
program arguments, but not in VM arguments.

public class TestLogger {

	public static void main(String[] args) {
	
		System.out.println( args[0] );
		
		String prop = System.getProperty( "java.util.logging.config.file");
		System.out.println( prop );
	}
}

The corresponding .launch is:

<?xml version="1.0" encoding="UTF-8"?>
<launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication">
<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="TestLogger"/>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS"
value="${project_loc}"/>
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="TestLogging"/>
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS"
value="-Djava.util.logging.config.file=${project_loc}/src/logging.properties"/>
<booleanAttribute key="org.eclipse.debug.core.appendEnvironmentVariables"
value="true"/>
</launchConfiguration>

Output is:
C:\dev\workspace\TestLogging
${project_loc}/src/logging.properties

Clearly, the second line should not read as it does.

WORSE STILL.  Further testing, trying to use ${workspace_loc:TestLogging} gave
teh exact same results as above (i.e. containing ${project_loc}