RC2 build #200201230331 of NetBeans 3.3.1 on Windows 2000 with JDK 1.4b91
Auto pre-commit functionality does not work if user launches IDE with user direc-
tory that contains at least one space in its path. The result is that commit tem-
plate is not generated and commit message is set to single new line character.
Steps to reproduce:
1. Launch IDE with -userdir "C:\Temporary folder\Test" switch.
2. Mount CVS filesystem using Command-line Client.
3. Modify some [Up-to-date] file so that it becomes [Locally Modified].
4. Right click this file and choose "CVS|Commit" popup menu item.
5. "Enter reason" textarea will be empty.
This is pure SPACE_IN_PATH problem that in this case concerns user
Well, the "wincat.bat", which is supplied as an editor to CVS contains
spaces in it's path. It's properly quoted for the shell, but CVS
probably interprets it in a bad way. I will try to experiment with the
quotation to find out whether there is some chance to get it to work.
If there is a bug in CVS executable (i.e. can not run editors which
have space in it's path), some workaround would have to be invented
(e.g. copy wincat.bat into the current folder each time pre-commit is
to be executed).
I didn't find any quotation combination, that would work. Even on
Unix, the editor command is not found when it contains spaces, I was
not able to find any suitable quotation. It seems, that cvs does not
work correctly whenever it's arguments contains spaces.
It seems, that the only possible workaround would be to detect whether
the path to wincat.bat contains spaces and if yes, copy wincat.bat to
the current working directory and remove it again after the command
Hints and other solutions appreciated.
Fixed by copying wincat.bat into the current working directory when
the home directory contains spaces.
Fixed in dev build Feb 21.
Cool. Verified in development build #200203080100 of NetBeans 3.4.
This fix needs to be backported to the sierra branch where
SPACE_IN_PATH is a supported feature.
closing since the bug is fixed in trunk, the SIERRA_FIX keyword is enough.
Sure. BTW, why did you Mark need it opened ?
I just wanted to make sure this appeared on the open bug list for
Sierra. I was under the impression that this would not happen if the
bug was marked FIXED, but Trung has since clarified that as long as
the S1S4.1 target milestone is -not- selected, this will be flagged as
open in that release (since the SIERRA_FIX keyword is set). Sorry for
Fixed in the sierra branch.
Confirming as fixed in Sierra build #020902_1 of Sun ONE Studio 4
The bug is steal in realease notes.
Resolved for 3.4.x or earlier, no new info since then -> closing.