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.
If I rename a java source file by only changing the case/capitalization, then the next time I run CVS > Show Changes, it will list the old file name in green as it were new. The new file name is able to be committed as expected, but the old name (which no longer exists in the file system) is floating around in NetBean's memory. I've tried CVS update and restarting NetBeans, but it still remembers the old file name. When I try to commit it any (to see what happens), nothing happens... probably because the new spelling is already up-to-date with CVS, so CVS probably ignores it. So, it seems to remain there forever. (I can trick NetBeans by deleting the new file and NetBeans' notion of the old file, commit it, then restore a copy I kept.) FYI, I'm using the CVS internal to NetBeans. I will attach a screen shot of the Window > Versioning > CVS window... Notice the difference in the letter 'P' in the file name. It is lower case in the "File" column, but upper case (correctly) in the "Location" column. Work Around: Never rename by changing case only. Instead, rename different, commit, then back to what you want, and commit again.
Created attachment 65656 [details] Netbeans is confused regarding case (notice the letter 'P' vs. 'p')
Mac file system (just like Windows file system) is not fully case-sensitive like other unixes and therefore it is not possible to handle such situations correctly. Your workaround is a correct procedure in this case. You could also remove and re-add such file again.
Understood, thanks! I'd like to suggest that NetBeans prevent or warn users for capitalization changes on OSes that behave this way. Especially since I found it very difficult to convince netbesns to recognize the filesystem version of the name once it got changed. Now that I understand I'll be OK next time but newbies may get very frustrated. Can we change this issue to an enhancement request?
We will think about it.
Came across this accidentally, but I must say I support this request. May prevent having hard times to some newbies ..