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

Bug 333747

Summary: Order of precedence for properties is incorrect. Command line should override
Product: z_Archived Reporter: Matthew Webber <matthew>
Component: BuckminsterAssignee: buckminster.core-inbox <buckminster.core-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: henrik.lindberg, thomas
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Matthew Webber CLA 2011-01-07 09:16:46 EST 
Build Identifier: BuckyBook v0.8

In BuckyBook v0.8:

* table 10.1 on page 113 Materialization property value precedence
This table is incorrect. The command line should override every other setting. My guess is that items 6-11 in the table should be moved to the top, and then the new 1 & 2 (6 and 7 in the existing table) should be swapped.

* table 10.2 on page 114 Action invocation property value precedence
This table is incorrect. The command line should override every other setting. 1 & 2 should be swapped.

Note that items 6-11 in table 10.1 are the same as table 10.2 (with the same error).

The order in these tables should be reviewed by someone who knows what they should be, since the existing tables are clearly wrong.

Reproducible: Always
Comment 1 Henrik Lindberg CLA 2011-03-05 13:47:29 EST 
Need input from Thomas to ensure that the information is correct.
Comment 2 Thomas Hallgren CLA 2011-03-06 04:56:36 EST 
The tables on page 113 and 114 are correct with one minor adjustment. The properties passed on the command line, whether it's a single property -Dxxx=yyy or a property file -P<filename> will be added (and override) in the order they are declared. So the last entry wins.

It is common to let command line declarations override and I think the fact that they don't should be considered a bug so I'm moving this bugzilla. We can create a documentation clone of it once the bug is fixed.
Comment 3 Thomas Hallgren CLA 2011-03-31 11:42:42 EDT 
*** Bug 333743 has been marked as a duplicate of this bug. ***