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

Bug 258300

Summary:	[mac][shared] [fwkadmin] Need to be smarter about processing eclipse.ini in shared mode
Product:	[Eclipse Project] Equinox	Reporter:	Simon Kaegi <simon_kaegi>
Component:	p2	Assignee:	Simon Kaegi <simon_kaegi>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	heidwill, overholt, pascal
Version:	3.5
Target Milestone:	3.6 M5
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Simon Kaegi

2008-12-10 10:43:36 EST

Currently we're setting a dummy eclipse.ini.ignored file as our launcher config file. We should instead use the existing eclipse.ini and look at having consistent logic with what the framework does in terms of location the user's configuration location. Also see bug 25130

Comment 1 Pascal Rapicault

2008-12-10 14:09:43 EST

I'm not sure what is the problem you are encountering nor what you would want to do, since even if the eclipse.ini in the user area contained new values it would not be read by the launcher.

Comment 2 Simon Kaegi

2008-12-16 15:39:33 EST

*** Bug 258365 has been marked as a duplicate of this bug. ***

Comment 3 Pascal Rapicault

2008-12-17 22:53:11 EST

See also bug #258365

Comment 4 Andrew Overholt

2009-03-12 14:58:23 EDT

I'm not sure that the user eclipse.ini has ever been usable like this.  I had someone ask me about it the other day, actually, and I just told them they had to edit the system-wide (read-only location for non-root users in RPM case) one.

Comment 5 Andrew Overholt

2009-04-27 12:33:27 EDT

Would this allow for per-user overrides of shared eclipse.ini properties?

Comment 6 Simon Kaegi

2009-04-27 15:23:15 EDT

(In reply to comment #5)
> Would this allow for per-user overrides of shared eclipse.ini properties?
No, this bug is more about getting our locations set right.

Comment 7 Simon Kaegi

2009-04-27 15:23:58 EDT

In particular I'd like to ensure we have the locations correct for the mac shared install.

Comment 8 Simon Kaegi

2010-01-18 17:33:48 EST

Talking to Andrew we suspect this bug has been fixed with the changes done for bug 280007 and bug 277553. Still need to verify.

Comment 9 Simon Kaegi

2010-01-19 20:30:18 EST

Pascal verified last night. Marking fixed.