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.
Using NB 6.0 build 200710020000 on Win XP and CVS (CVSNT 2.5.03 B2382) when you try to rename a source file changing only the case, CVS behave in a wrong manner. To produce the problem I followed the steps below: - I renamed a file from i.e PackPayload.java to Packpayload.java using NB refactoring tool (the CVS panel showed only PackPayload.java marked as locally deleted) - I tried to execute “commit all” and I got the error shown in the attached image - Then I executed a "refresh status" and in the CVS panel I saw only PackPayload.java locally modified - I committed all - I simply changed the source inside Packpayload.java - I performed a clean and build - At that point the CVS panel showed Packpayload.java locally modified so I executed a "commit all" - A refresh status, without doing anything else got as result Packpayload.java remotely modified to change source and commit changes I had to follow and repeat the sequence update edit the file commit refresh status As Travis Risner explained, this isn't due to a NB's bug but, as suggested by Fabrizio Giudici, the IDE should manage the case to avoid messy repository states.
Created attachment 50308 [details] Commit Error
Confirmed this happens with NetBeans 8.1, Mac OS X, Mercurial as well. Created a file, Flightplan_DPA.xml Renamed the file to Flightplan_Dpa.xml Netbeans is showing Flightplan_DPA.xml is new (the file no longer exists) hg on the command line shows Flightplan_Dpa.xml is new. Version Control module should correctly list Flightplan_Dpa.xml as a new file to be added to version control.
Created attachment 158257 [details] VCS case change error Screenshot of VCS module case change issue, created with Mac OS X and Mercurial, NetBeans 8.1
Confirmed Workaround: - Commit everything via command line, or command/ctrl click on only the correct files in NetBeans, and perform a commit leaving out the incorrect case file shown as new. - Then restart netbeans (The problem only exists in NetBeans memory) I suspect this bug affects ALL hardware, ALL platforms, ALL VCS systems, on which NetBeans can run on a case sensitive filesystem.
This bug was filed against CVS, not Mercurial, do not switch categories deliberately.
BTW, your problem with Mercurial is this one probably: bug 219782.
> This bug was filed against CVS, not Mercurial, > do not switch categories deliberately. Sorry about that. This bug was also filed in 2007 for NetBeans version 6. > BTW, your problem with Mercurial is this one probably: bug 219782. No, actually it's not. I didn't commit, nor did I use refactor->rename, though the commit fails if you try it with the incorrect case filename because obviously the file shown by NetBeans does not exist in the filesystem. Please note, as I mentioned, I believe this bug to be present for all version control implemented by NetBeans, since at least version 6, nine years now. There is no "ALL" option in the Product: Versioncontrol Component: dropdown. If there were, I believe it would be correct. I have been able to replicate this bug on a case sensitive filesystem with Netbeans using Subversion, Git and Mercurial (and, with the OP's filing for CVS, that tends to imply all VCS are affected)
Then file a fresh new bug against Versioncontrol/Code, but do not touch CVS issues, since these are prehistoric bugs, the cause is for 99% a different one.