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

Bug 32026

Summary:	should try alternative writable-location when log cannot be written
Product:	[Eclipse Project] Equinox	Reporter:	Rafael Chaves <eclipse>
Component:	Incubator	Assignee:	User Unknown <unknown1>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	artho
Version:	unspecified
Target Milestone:	3.0 M9
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Rafael Chaves

2003-02-17 11:43:07 EST

2.1 RC0

We should look for an alternative location where to write the log to when we 
have problems writing to the default location (under the workspace metadata 
area). When starting Eclipse with an unwritable location for the workspace, a 
message will be presented telling the user to look for the reason in the log 
file, which won't exist, of course.

We should try to write to user.dir, for instance.

Comment 1 DJ Houghton

2003-03-18 13:50:58 EST

See also bug 33976.

Comment 2 Rafael Chaves

2003-08-21 12:06:09 EDT

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

Comment 3 DJ Houghton

2004-04-14 16:20:39 EDT

Log writing is done in the OSGi layer now.

Comment 4 Jeff McAffer

2004-04-15 14:15:02 EDT

The new runtime looks for writeable places for the configuraiton area.  In a 
shared install scenario this would end up being in the user's home dir 
somewhere.  If the instance (workspace)location is not know, the log is written 
to this configuration area.  If it is known, then presumably it is in some 
writable area so putting the log in the workspace/.metadata area is ok.

Closing