Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333743

Summary: property keys specified on the headless IMPORT command do not override values specified in the CQUERY
Product: z_Archived Reporter: Matthew Webber <matthew>
Component: BuckminsterAssignee: buckminster.core-inbox <buckminster.core-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: info, matthew, thomas, tony
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Matthew Webber CLA 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
Comment 1 Anthony Wallace CLA 2011-02-11 09:46:33 EST
I am also coming across the same behaviour as descibed above on win32.
Comment 2 Thomas Hallgren CLA 2011-03-31 11:42:42 EDT

*** This bug has been marked as a duplicate of bug 333747 ***