Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 3100 - [resources] CoreFileSystemLibrary.isReadOnly() implemented in pure Java is not precise (1GI9BUE)
Summary: [resources] CoreFileSystemLibrary.isReadOnly() implemented in pure Java is no...
Status: RESOLVED DUPLICATE of bug 12769
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.1 M4   Edit
Assignee: Rafael Chaves CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:49 EDT by Rodrigo Peretti CLA
Modified: 2002-12-03 18:03 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rodrigo Peretti CLA 2001-10-10 22:49:26 EDT 
The CoreFileSystemLibrary.isReadOnly() method implemented in pure Java
(no core library available) is not precise enough. It uses the java.io.File.canWrite
method. For example, this method also returns false if the file name size is longer
than the permited one.
	This question raised when running Eclipse on Neutrino. The message that showed
up in the dialog was that the file could not be written because it was read-only but
the real reason was that the file path was too long.

NOTES:
Comment 1 DJ Houghton CLA 2001-10-24 06:44:23 EDT 
PRODUCT VERSION:
	129
Comment 2 DJ Houghton CLA 2002-01-08 14:34:19 EST 
Not a committed item on the 2.0 plan.
Changing resolution to LATER.
Comment 3 DJ Houghton CLA 2002-09-10 12:02:40 EDT 
Reopening for investigation.
Comment 4 DJ Houghton CLA 2002-12-03 18:03:43 EST 

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