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.
dev build 200312031900 Can't use JavaCVS because of issue #37753 and can't use the Generic VCS engine because it requires an external CVS.EXE engine. Even after you select USE INTERNAL CLIENT it refuses to work and keeps on looking for CVS.EXE
O.K. I'm currently working on the CVS profile for Generic VCS. I'm changing the dialogs and set of the commands so that when you select the built-in client it should work similar to JavaCVS module. You're right that not all commands work correctly when built-in client is selected. I simply did not count with the possibility that JavaCVS becomes absolutely unusable. I'm concentrating on getting the CVS profile to work.
Update: All commands on the popup menu should work O.K. in tomorrow's dev build. The only exception is graphical diff, where one file is shifted by several lines. This shift will be fixed as soon as issue #37843 is fixed. Commands on Versioning Explorer (now "VCS Filesystems") still use cvs.exe. I will work on this tomorrow.
Commands acting on VCS Filesystems fixed in trunk: /cvs/vcsgeneric/profiles/cvsprofiles/src/org/netbeans/modules/vcs/profiles/cvsprofiles/config/cvs.xml,v <-- cvs.xml new revision: 1.13; previous revision: 1.12 So now, when you select the built-in client, cvs.exe should not be used at all.
OK in the current NB36 dev