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 had mounted the source the the JDK that were in a JDK installation directory. I uninstalled that JDK and the next start of NetBeans gave me exception that said: Cannot read class: org.netbeans.core.ExJarFileSystem This is a very cryptic message since the name of the filesystem is not mentioned. Seems like this sitiuation can be handled much more gracefully. I would recommend a warning popup that says something like: Jar file <jar-file-name> was mounted but is now missing so it can't be remounted. [ok] Another approach would be to do a "psuedo mount", so the name shows up in the explorer, but use an icon badge or some other visual indicator to show that it could not be found. As it was, I had to do a Show Details on the exception and look through that for a while in order to find the name of the jar file. I will attach the full text of the exception.
Created attachment 8188 [details] Exception stack trace
I would guess openide/settings. The most inner exception is annotated correctly, but the after that a new (less descriptive) annotation is added.
I find this behavior very annoying, especially since there is no way (within the IDE at least) to remove the missing mounts, causing the exception dialog to pop up during each restart and during new mounts. The only workaround I know of is to either a) recreate the project or b) shut down NB and edit the project on the disk manually. Both workarounds are lousy. It is so common for evolving projects to change JAR files, and having to remember to unmount the JARs _before_ the project is updated locally is something the developer should not have to worry about.
I agree with Gudmundur that this is very annoying. What I did was to place a jar file into the correct path so the IDE would come up and then unmount the jar file. None of the workarounds are pretty. Should we consider raising it to a P2?
Definitely can't be solved in settings, because settings are too general and can't handle every object in differnet manner. Also filesystems can't do better, because exception is correctly annotated and contains all necessary information. So, for presentation is responsible AutomountSupport. Against AutomountSupport was already reported bug #26072, which was already fixed and verified. Marked as duplicate. According to fix, then exception should not pop up during each restart. *** This issue has been marked as a duplicate of 26072 ***
verified, closed - it's duplicate.