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.
Discovered in: CE/IE Build 1099 on Windows 2000, Red Hat Linux 6.5, Solaris 5.8 ============== (all with JDK1.3) Description: ============ If some node in tree view of the explorer doesn't have its source java file it is unable to be parsed. That's okay. But if this source file is placed to the right location its node in tree view still remains with red cross symbol and message "Error". User would sure appreciate if this node becomes parsable after the correction of missing source file problem. Steps to reproduce: =================== 1. Mount some existing CVS filesystem or create brand-new one. 2. Underneath create some parsable file e.g. new javabean from template. 3. Add it and commit it into the repository and then delete it. 4. On the root node of the CVS filesystem refresh its contents via CVS/Refresh menu item. After that the file will be in [Needs Checkout] status. 6. On this file perform "Check Out" command of CVS menu. Although the status is changed to [Up-to-date] it is still unable to be parsed.
Everything is better now, but I still have specific case that doesn't parse the file although it has already been checked out. The problem comes round in other Generic VCS filesystems that our IDE supports (PVCS, VSS). The status of file that is not checked out is [Missing] there. For the reproduction of this bug it is necessary to have either PVCS or VSS installed. But there is one twist: let's use feature of Generic VCS - Variables that besides other stuff enables you to change possible statuses of files. So do the following: 1. Mount some existing Generic VCS filesystem or create brand-new one. 2. Invoke Customizer dialog of this CVS FS and click on "Variables" property. 3. Select "POSSIBLE_FILE_STATUSES_LOCALIZED" variable and click on "Edit..." button. 4. In "Variable value" textfield change "Needs Checkout" to "Missing" and click on "OK" button. The same way close "Property Editor: Varibles" and Customizer as well. 5. Now under this CVS FS create new parsable file e.g. javabean. 6. Add it and commit it into the repository and then delete it. 7. On the root node of the CVS filesystem refresh its contents via CVS/Refresh menu item. After that the file will be in [Missing] status. 8. On this file perform "Check Out" command of CVS menu. Although the status is changed to [Up-to-date] it is still unable to be parsed.
[build 1126] Reproduce the bug if you [or others] can. Things are even worse - I can not find relevant change, that might fix the bug, made after the time you've updated the info.
Resolved for 3.3.x or earlier, no new info since then -> closing.
Resolved for 3.4.x or earlier, no new info since then -> closing.