Description Matthew Webber 2011-01-07 08:47:36 EST

Build Identifier: org.eclipse.buckminster.cmdline=1.0.350.r11559 org.eclipse.buckminster.core=1.2.361.r11621 org.eclipse.buckminster.installer=1.1.0.r11559

** PROBLEM 1 **
I run headless buckminster with the following command:
import '-Dpropertyname=commandlinevalue' 'http://myserver/my.cquery'

The CQUERY points to an RMAP, which references ${propertyname}.
propertyname is defined in the RMAP (with mutable="true").

If propertyname is NOT defined in the CQUERY, then the value specified on the command line (if present) overrides the value specified in the RMAP - this is correct. This shows that the command line is being parsed correctly.

If propertyname IS defined in the CQUERY, then any value specified on the command line is ignored, and the value specified in the CQUERY is applied - this is not correct behaviour. Whatever is in the CQUERY incorrectly overrides the command line, this is irrespective of whether the property is defined at te top level, or in an advisor node.

** PROBLEM 2 **
I run headless buckminster with the following command:
import -P /home/bmn54829/.gda/deploy.properties 'http://myserver/software/buckminster/gda_target.cquery'

If a properties file is NOT defined in the CQUERY, then the value specified on the command line (if present) is used - this is correct. This shows that the command line is being parsed correctly.

If a properties file IS defined in the CQUERY, then any value specified on the command line is ignored, and the filename specified in the CQUERY is used (even if the file does not exist) - this is not correct behaviour. Whatever is in the CQUERY incorrectly overrides the command line.

** OBSERVATIONS **
These two problems are likely symptoms of the same underlying cause.


Reproducible: Always