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.
I am seeing a FSException regarding a jar that was deleted outside of the ide on startup. The full log and exception info are attached. The issue can be resolved by going into the explorer customize dialog and removing the obsolete link. Should this just be done automatically, possibly after a warning dialog?
Created attachment 6922 [details] the ide.log
This problem occures during deserialization of filesystem from .settings file, reassigning to openide/filesystems.
*** Issue 26088 has been marked as a duplicate of this issue. ***
Probably should be annotated in filesystems with USER or WARNING severity, then AutoMountSupport should right notify and unmount such currupted filesystem. Because in filesystems already implemented, then reassigned to AutomountSupport.
*** Issue 26535 has been marked as a duplicate of this issue. ***
*** Issue 24568 has been marked as a duplicate of this issue. ***
Users frequently complain about the lack of robustness here - if NB knows the setting is corrupt, why does it leave it on disk and keep reporting the same error on every startup? Suggest it be considered for a hypothetical 3.4.1.
*** Issue 26623 has been marked as a duplicate of this issue. ***
*** Issue 27442 has been marked as a duplicate of this issue. ***
I increased priority because many users reports this problem and it is not too dificult to fix it.
*** Issue 26391 has been marked as a duplicate of this issue. ***
*** Issue 27445 has been marked as a duplicate of this issue. ***
Checking in src/org/netbeans/core/AutomountSupport.java; /cvs/core/src/org/netbeans/core/AutomountSupport.java,v <-- AutomountSupport.java new revision: 1.47; previous revision: 1.46 done
I am not sure if the best idea is to unmount corrupted filesystems. Why corrupted LocalFilesystem can be mounted in repository and market as invalid? Why JarFileSystem throws exception on deserialization? It can be marked as invalid too.
The file is not there --> filesystem makes no sense --> message is written to the log and the filesystem is unmounted. If you disagree please consult nbui, wait for an agreement and then reopen the issue. Thanks.
Platform/OS independent issue.
*** Issue 28014 has been marked as a duplicate of this issue. ***
verified
*** Issue 27464 has been marked as a duplicate of this issue. ***
Hi. This issue is marked as 3.4.1_CANDIDATE. It means that it should be integrated into release341 one branch. The plan at http://www.netbeans.org/devhome/docs/releases/34/index.html expected beta1 to be produced on Dec01. That did not happen due to a lot of outstanding not integrated candidates like this one. Would it be possible to spend few minutes by backporting this fix? Thank you in advance.
Fixed in 341. AutomountSupport 1.45.46.1.
*** Issue 29279 has been marked as a duplicate of this issue. ***
*** Issue 29343 has been marked as a duplicate of this issue. ***
*** Issue 27893 has been marked as a duplicate of this issue. ***
*** Issue 28966 has been marked as a duplicate of this issue. ***
Resolved for 3.4.x or earlier, no new info since then -> closing.