| Summary: | CoreFileSystemLibrary.isReadOnly(String) doesn't work for new files if no natives | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jerome Lanneluc <jerome_lanneluc> |
| Component: | Resources | Assignee: | DJ Houghton <dj.houghton> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | hroark, rodrigo |
| Version: | 2.0 | ||
| Target Milestone: | 2.0 M5 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Jerome Lanneluc
The implementation defaults to java.io.File behaviour; essentially: return !new java.io.File(filename).canWrite(); java.io.File.canWrite() is spec'd to return false if the file doesn't exist. I have tried this in a scrapbook and it works ok. (Win98) Will try in Win2K to see what we get. I agree that java.io.File.canWrite() is working as expected. I just think that its usage is wrong (in the case of a non-existing file) if we want to have the same behavior as: isSet(getStat(fileName), STAT_READ_ONLY); Oops...now I see what you mean. Sorry. isReadOnly() should return false for a non-existing file but using canWrite() returns true. Fixed and released. Available in builds > 2002-04-09. *** Bug 12979 has been marked as a duplicate of this bug. *** bug 12979 was marked as a dup, but the problem still exists in 4/10 build... Try an integration build after 2002-04-09. |