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 199895 - Netbeans cannot follow symbolic link when browsing librairies
Summary: Netbeans cannot follow symbolic link when browsing librairies
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 7.0.1
Hardware: All All
: P2 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-05 10:59 UTC by FoxXav
Modified: 2011-07-13 13:16 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description FoxXav 2011-07-05 10:59:12 UTC 
Product Version = NetBeans IDE 7.0.1 RC1 (Build 201106222100)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.6.0_26
Runtime = Java HotSpot(TM) 64-Bit Server VM 20.1-b02

We use symbolic link (we try with both junction and symbolic) in our projects. And we move to win7 64bits few days ago, and we notice that netbeans cannot navigate into file system when using symbolic link in the path.
To be more precise, when open a project, the fileChooser allow us to go threw the symbolic link (great), but when browsing for libraries (add JAR/Folder for instance) we cannot go threw symbolic link.

I try to put -J-Dnb.FileChooser.useShellFolder=false in netbeans.conf but it didn't do anything.
I also try with the new JDK7 but there is the same issu.

I hope there is a solution as we really need to use symbolic links

FoxXav
Comment 1 Jiri Rechtacek 2011-07-13 08:53:27 UTC 
Stando, could you look on it on 64bits Win7? Thank you
Comment 2 Stanislav Aubrecht 2011-07-13 09:01:49 UTC 
i tried file choose in swingset demo and the symbolic link isn't accepted either
win 7 64bit, jdk 1.6.0-24
Comment 3 Jiri Rechtacek 2011-07-13 13:16:10 UTC 
seems to be already tracked as jdk bug id 4906607