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.

Bug 15591 - '.' jarfile mounted after ide restart
Summary: '.' jarfile mounted after ide restart
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Sun SunOS
: P3 blocker (vote)
Assignee: rmatous
URL:
Keywords:
: 15545 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-09-18 15:09 UTC by Jan Zajicek
Modified: 2008-12-22 23:27 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Zajicek 2001-09-18 15:09:40 UTC
Steps:

1.mount some jar files
2.exit ide
3.delete the jar files
4.start ide
5.you will see '.' mounted instead of 'unreachable filesystem' or something simmilar
Comment 1 Jaroslav Tulach 2001-09-19 14:13:08 UTC

Radek please improve the display name of the filesystem when no jar
file is selected. I guess that should be the cause of the problem.

import org.openide.filesystems.*;
Repository.getDefault ().addFileSystem (new JarFileSystem ());

Comment 2 Jan Zajicek 2001-10-10 10:57:44 UTC
*** Issue 15545 has been marked as a duplicate of this issue. ***
Comment 3 _ ttran 2001-10-25 14:33:53 UTC
in this case I would rather remove the non-existing FS from the list
of mounted FS.  What kind of benefit the user has from seeing
something like "<deleted jarfile>" in the Filesystems tree?  Can she
change the mount point of the FS?  Can she find out the original mount
point?
Comment 4 rmatous 2001-10-26 14:54:43 UTC
One idea. User may have all mounted filesystems located on removable 
media that doesn`t need to be present in OS at the moment. Then 
filesystems disappear and user must mount them again. 
Comment 5 rmatous 2001-10-30 09:36:18 UTC
Fixed in trunk (JarFileSystem.java rev. 1.58).To keep continuity of 
previous behaviour and because of my previous comment, I changed 
getDisplayName method to label invalid JarFileSystem.
Comment 6 Marian Mirilovic 2002-05-24 15:45:07 UTC
verified in [nb_dev](20020524), "Invalid JAR" shown instead.
Comment 7 Quality Engineering 2003-07-01 16:51:16 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.