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 23403 - no property info for jar path in explorer/filesystems - lostjar info
Summary: no property info for jar path in explorer/filesystems - lostjar info
Status: CLOSED DUPLICATE of bug 18988
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: akemr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-13 13:36 UTC by tek
Modified: 2008-12-22 16:51 UTC (History)
0 users

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 tek 2002-05-13 13:36:18 UTC
is it possible to display the path of the jar files that are mounted in 
explorer/filesystems in the same manner as mounted directories?

in recently switching computers where the drive where nb is installed differs, 
explorer/filesystems displayed "Invalid c:\dev\dirA" for invalid directories.  if 
i clicked on the invalid directory in the explorer, it's directory path was 
displayed in the "Root Directory" property in the properties window.  i was 
able to fix my directories by editting the "Root Directory" property and 
changing the "c:" (drive) to "d:".

however, clicking on an "Invalid JAR" doesn't give its "Root Directory" in 
the properties windows, so i have no idea what jar it was.  i have to now 
guess which jars i was using for the project.

is there a workaround, or can a fix for this be implemented in nb3.4?

thank you.
Comment 1 akemr 2002-05-13 13:49:53 UTC
Filesystems subcomponent, however it's duplicate of #18988

*** This issue has been marked as a duplicate of 18988 ***
Comment 2 Quality Engineering 2003-07-01 15:56:39 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified
Comment 3 Quality Engineering 2003-07-01 16:16:45 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.