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.
This problem was originally reported by Daniel Mladek in the issue #9716. Since this problem has no connection to the issue #9716, I'm creating this new one. Description copied from issue #9716: My name's file is: poli's cosum! frtku'js.txt Here is tho command output: =========================== /bin/sh -c "cd \"/home/dm103276/.A/Build.Test/CVS/testonly/w6/\"; \"cvs\" -d \":local:/home/dm103276/.A/Build.Test/CVS/testonly/r1\" -f commit -F \"/tmp/tempCommit39304output\" \"ble/poli's\" \"ble/cosum!\" \"ble/frtku'js.txt\" " cvs commit: nothing known about `ble/poli's' cvs commit: nothing known about `ble/cosum!' cvs commit: nothing known about `ble/frtku'js.txt' cvs [commit aborted]: correct above errors first!
Fixed in the main trunk. Shoud this go also to Pilsen FCS? Probably yes, because it prevents the user from being able to commit a file, which contain spaces in it's name. Would you please test this carefully, so that we can be sure, that we do not incorporate any instability to the Pilsen build? Thanks.
Thank you Martin for entering a new bug for that. Originaly I thougtht that it was the same problem. Verified on [NBdev-200106220100]
Fixed in pilsen_fcs branch.
[REGRESION] oupss! I must reopen it:-( today I discovered on [Pilsen-010626_1] and CVS (p)server only? on cvs 1.11 imposibility to commit MDO -> form+java. I had specified Relative mountpoint and use this connection: pserrver:fortecvs user:dmladek repository:/testrepo checkouted module:dmladek rel.mount:scratch --------------------------------------- It doesn't work too if you have no rel.mountpoint. Probably cvs server return different path then local cvs so the previous fix isn't able recognize 2 files couse it thinks thet it is one file. ------------------------------------------------------------- I'm too sorry, but this fixed I've tested only localy:-((( My mistake...
Thanks for catching this! Well, it should be more robust now. Fixed again in the main trunk.
in the main trunk [NBdev-200106290100] it is OK. Let mi know when it will be commited into Pilsen branch too. Thsnks
Fixed in the pilsen_fcs branch.