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: | org.netbeans.modules.masterfs.filebasedfs.utils.FSException: Cannot delete file SONIA in Y:/sites/all/modules/science/research_data/lib. | ||
---|---|---|---|
Product: | java | Reporter: | Exceptions Reporter <exceptions_reporter> |
Component: | Refactoring | Assignee: | Ralph Ruijs <ralphbenjamin> |
Status: | NEW --- | ||
Severity: | normal | CC: | j0inty, jtulach, marco_bresciani, ralphbenjamin, rocksero3ml, sreimers |
Priority: | P3 | ||
Version: | 7.1 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 134153 |
Attachments: | stacktrace |
Description
Exceptions Reporter
2012-09-10 05:02:33 UTC
Created attachment 124074 [details]
stacktrace
I do not understand why you reassigned this to refactoring. Only one report from the exception reporter is from safe delete, but all others are from different places. Shouldn't we try to fix this in core, instead of all api users? Right, I looked only at this one report. How should I fix this in core? You ask an I/O and the I/O fails you get an IOException (FSException is subclass). The exception contains localized message. Can you tell me what else the filesystems are supposed to do? It is responsibility of the caller (refactoring in this case) to present this failure in a nice way, so users don't report this as a system error. What do you use to report the exception? core can certainly help you report the exception in a nice way, but that is a job for other core components, not for filesystems. SafeDeleteAction is using plain logger to report the exception: LOGGER.log(Level.WARNING, null, ioe); that is wrong. You are not facing a NetBeans system problem to report the exception this way. What alternative you would find most suitable after reading http://bits.netbeans.org/dev/javadoc/org-openide-util/org/openide/util/doc-files/logging.html ? |