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.
dev build 200411211900 JDK 1.5 There is a *very* annoying usability problem with the "add jar/folder" button in the library manager. Because you allow the selection of directories, it is impossible to enter: "c:\program files<enter>" in order to quickly navigate to that directory in order to choose a JAR file. By splitting up the button into two separate options, you can have the JAR chooser expect only files (not directories) and this will allow better keyboard navigation. Currently it is an absolute nightmare to enter JAR paths using the file-chooser. Using the mouse is too slow.
Jano? Maybe something to consider during the design of ui redesign. However it would be just a workaround for the bad usability of JFileChooser.
Probably WONTFIX, though we are continuing to push on the Swing team to produce a better UI for JFileChooser which would actually work for directory selection mode.
Jesse, I specifically remember filing a bug against the JDK for this issue and they told me that as far as they are concerned there is no such problem/bug because if your JFileChooser allows the input of directories then the current behavior is "correct". As such, are we really sure they are aware we are pushing for this? I expect that even if JFileChooser allows the input of directories I have to explicitly hit "open" for the JFileChooser to close -- as opposed to the current behavior where entering the path in the text field and pressing enter closes the JFileChooser immediately. The required change is: hitting enter in the text field does not close the JFileChooser.
Once in a while (or even more often), there is a type of question on the nb users mailinglist when people report the "bug" that "add jar/folder" doesn't work when they're adding a folder full of jars. The IDE reacts correctly and puts the folder on the classpath (NOT the jars within the folder) - but users expect that the jars are added to the classpath (as the button also says "add jar/folder"). I'd propose to either add jars in a folder automatically to the classpath (and do what a user would expect) OR split the button into "add jar" and "add folder". I think that'd be much more obvious.