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.
Summary: | CVS: COMMIT_TEMPLATE_GETTER fails if user dir contains spaces. | ||
---|---|---|---|
Product: | obsolete | Reporter: | Jiri Kovalsky <jkovalsky> |
Component: | vcsgeneric | Assignee: | Martin Entlicher <mentlicher> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | markdey |
Priority: | P3 | Keywords: | SPACE_IN_PATH |
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jiri Kovalsky
2002-01-23 11:18:22 UTC
This is pure SPACE_IN_PATH problem that in this case concerns user directory. 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 finishes. 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 any confusion. Fixed in the sierra branch. Confirming as fixed in Sierra build #020902_1 of Sun ONE Studio 4 update 1. The bug is steal in realease notes. Resolved for 3.4.x or earlier, no new info since then -> closing. |