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

Bug 330611

Summary:	[launcher] Add mechanism for ignoring user specified config.ini values
Product:	[Eclipse Project] Equinox	Reporter:	DJ Houghton <dj.houghton>
Component:	Launcher	Assignee:	DJ Houghton <dj.houghton>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	john.arthorne, stephen.francisco, tjwatson
Version:	3.6.1
Target Milestone:	3.6.2
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:
Bug Depends on:	330133
Bug Blocks:

Description DJ Houghton

2010-11-18 16:01:12 EST

Cloned to track release into Eclipse 3.6.x stream.

+++ This bug was initially created as a clone of Bug #330133 +++

Tom and I were talking about the problem where we have a shared install and the user has values in their config.ini which cause the install to not load. (for instance after the root user has updated the shared install)

One approach to this would be to implement a mechanism where by the user config.ini values for certain properties could be ignored. 

We've agreed to the following approach:
- we will look for <propertyname>.override.user
- it can be set either in the config.ini from the shared location or by a -D parm on the command line
- if the override property is set (to be any value: getProperty() != null) then the value from the shared install area will override any value from the user config.ini
- if a property value is set via the command-line (e.g. -Dkey=value) then that value will not be over-written

Comment 1 DJ Houghton

2010-11-22 13:58:28 EST

Released into 3.6.2 branch.
Closing.