This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Moving package (if contains at least one read only file) couses lost of your DATA !!! (FSException is thrown) | ||
---|---|---|---|
Product: | platform | Reporter: | dmladek <dmladek> |
Component: | -- Other -- | Assignee: | akemr <akemr> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | jchalupa, jtulach, mbalin, sdedic |
Priority: | P1 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
dmladek
2000-11-16 16:07:29 UTC
The real cause of that bug is that java.io.File.delete() does its job EVEN IF the file being deleted is set to read-only in the host OS. *** Bug 8447 has been marked as a duplicate of this bug. *** The problem is that DataFolder.handleMove removes the folder even if there were
some problems when moving of the contents. I suggest that when there are any
problems with moving the content the original folder will not be removed.
suggested change in code:
< fo.delete (lock);
> if (problem == null) {
> // delete only if all files were moved
> fo.delete (lock);
> }
BTW: notification about problems during move should be nicer (not only display
Exception to the user)
[Boston-1159, Trunk-77, Release31-14] The problem is already solved by re-throwing IOException from child operation(s) before fo.delete(lock); Fixes were propagated to all branches today. The ugly display is caused by bug in ErrorManager that does not extract localized message correctly if the exception defines localized message, but is not annotated. verified on [1160CE Boston FCS] Resolved for 3.4.x or earlier, no new info since then -> closing. |