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.
it's impossible to use the subversion module together with a cygwin cmd line client. Because running on windows the netbeans svn module passes the svn commands in a format the cygwin client doesn't seem able to process. it would be nice to know what's the client ("pure" windows, or cygwin) on the cmd line to give at least a undestandable error message. maybe having an option for this, so the user could specify what client he has installed, would be the solution. The svn module could the work as if running against a linux shell. see also issue #108069
*** Issue 108536 has been marked as a duplicate of this issue. ***
*** Issue 124537 has been marked as a duplicate of this issue. ***
Is it documented that NetBeans subversion support does not work if Cygwin is installed? If not, can we have a note to that effect on subversion.netbeans.org? It took me a long time to figure out what the problem was.
agree. the faq and the online tutorial seem to be good candidates
I've added a brief note to the tutorial: http://www.netbeans.org/kb/60/ide/subversion.html (Note that changes should be visible by 11.1)
*** Issue 124343 has been marked as a duplicate of this issue. ***
*** Issue 144021 has been marked as a duplicate of this issue. ***
we won't support this - doesn't seem to be that much in demand anymore
Ran into this recently and debugged into it. Bottom line: * NetBeans passes paths in Windows notation, i.e. using backslashes and drive letters * The Cygwin version of svn.exe expects forward slashes and (in some cases) /cygdrive/d/... instead of d:/... Details can be found at http://www.clausbrod.de/Blog/DefinePrivatePublic20100424NetBeansVersusCygwin. I also posted a debugging/interceptor tool there which I used to learn about the interaction between the IDE and svn.exe, and to tweak paths as they are sent from NetBeans to svn.exe.
*** Bug 185790 has been marked as a duplicate of this bug. ***