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.
System Info: Product Version = NetBeans IDE Dev (Build 200410261800) Operating System = Windows XP version 5.1 running on x86 Java; VM; Vendor = 1.5.0_01-ea; Java HotSpot(TM) Client VM 1.5.0_01-ea-b04; Sun Microsystems Inc. Steps: 1. Register new e.g. VSS veriosned directory. 2. Check out some sources from repository. 3. Select some file node in Versioning tab of the explorer and invoke "Inlude in VCS Group | <Default Group>" menu action. 4. Switch to "VCS Groups" tab of the explorer and open this file to Editor. After these steps "Scanning Project Classpaths" dialog shows up.
And this is a defect? I guess it's by design, Java module probably needs to know the classpath... Scanning the classpath is certainly not initiated by VCS.
This is a correct behavior approved by UI team (Jano). If a file from an existing project (that is not open) is opened, the classpath of the parent project is scanned.
But is it correct in case there is no project open? I've only registered new versioned directory and open file in editor using VCS Groups.
It is correct if the file you opened in the editor is part of a project (even if the project is not open).
Verified.