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.
[ BUILD # : 200809091401 ] [ JDK VERSION : other ] Product Version: NetBeans IDE Dev (Build 200809091401) Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b15 System: Windows Vista version 6.0 running on x86; Cp1252; en_IN (nb) Steps to reproduce: 1.) Create new Web project 2.) Right-click -> Properties -> Libraries -> Add jar for say C: \mail.jar and C:\activation.jar and press OK 3.) Close the project in netbeans 4.) delete the libraries from C:\ 5.) Open the project in netbeans... This will ask to resolve reference problems 6.) Right-click on project and select Resolve Reference Problems 7.) Click Resolve button on 1st item activation.jar 8.) Browse dialog opens and select any folder and press OK. It will say that the problem is resolved, but actually activation.jar has not been found in the selected folder. This is incorrect behavior. Until the same library is not found, the problem should not be resolved.
reassigning to web. in my opinion the behaviour is correct, both jars and folders are classpath roots. if you select folder, well you probably have the activation.jar classes in a folder structure rather than a jar file. up to the user to decide.
OK...let me restate what the issue is... when I select any random folder (which does not contain the libraries/jar, which are actual references), even then netbeans thinks that the references are resolved, which in context of a project can be very dangerous. This is not just a web project issue, but for all kinds of projects... So should be reassigned to "projects"
The problem is that when a reference is broken all what's known about the reference is its name which in theory can be anything as well. It is difficult to give any guidance to user what to chose. Classpath item can be jar or folder with classes. Similarly you could argue that broken reference to activation.jar can be resolved to jakarta-commons-lang.jar and IDE will let user do that. Hopefully with sharable libraries feature (since NB6.1) this problem should not be that common - your references just will not get broken. Also as you may know you can always go to project's properties to libraries panel and fix classpath there if you resolved something wrongly. That reminds me that we have long term plan to get rid of "Resolve Broken References" dialog completely and merge the feature with Libraries panel in project properties - you would resolve broken references directly there.
Created attachment 153175 [details] C:\Program Files\NetBeans 8.0.2\bin
Created attachment 153176 [details] C:\Program Files\NetBeans 8.0.2\bin