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.

Bug 79923 - CVS -> Show Changes failed
Summary: CVS -> Show Changes failed
Status: RESOLVED WORKSFORME
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: CVS (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker with 1 vote (vote)
Assignee: issues@versioncontrol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-10 17:15 UTC by ulfzibis
Modified: 2007-01-04 17:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ulfzibis 2006-07-10 17:15:01 UTC
See attachment:
http://www.netbeans.org/nonav/issues/showattachment.cgi/31542/NetBeans%20Issue%2079471.jpg

See log files:
http://www.netbeans.org/nonav/issues/showattachment.cgi/31539/messages.log
http://www.netbeans.org/nonav/issues/showattachment.cgi/31543/messages.log

NB: Build 200606151230
- Master Filesystem: 1.8.12
- Diff: 1.15.11.42
- Subversion: 1.1
- CVS Versioning system: 1.7.11.1.42.1
Comment 1 Peter Pis 2006-07-11 12:42:14 UTC
Reassigning to "javacvs". Could you please provide us more details? Some
reproducible step would be really appreciated. 
Comment 2 ulfzibis 2006-07-11 16:00:31 UTC
There is only 1 step:
clicking on CVS -> Show Changes, when focus is on project root.

Comment 3 Peter Pis 2006-07-11 16:20:50 UTC
Sorry, for me it works fine. What kind of access method for repository
connection do you use? (pserver, local, ...) What type of project is that?
Comment 4 ulfzibis 2006-07-11 16:38:56 UTC
How can I find out this, because there is no Versioning Manager under the new
CVS client?

I think, that there is nothing special about the project.

The working copy worked fine under the old cvs-support under NB 5.0

Comment 5 Peter Pis 2006-07-11 17:01:09 UTC
Just invoke "Output" window.(Ctrl-4) and there should be some tabs (e.g.
:pserver:...). Invoke some "CVS" action and it should print its output into
appropriate tab.

Project types: web project, j2se, j2me, freeform ...
Comment 6 ulfzibis 2006-07-11 18:08:23 UTC
:local:C:\...

IDE:-------------------------------------------------
IDE: [11.07.06 17:28] Refreshing CVS Status started
cvs server: connect to 127.0.0.1(127.0.0.1):2402 failed: Es konnte keine
Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. 
cvs [server aborted]: Couldn't connect to lock server
 
IDE: [11.07.06 17:28] Refreshing CVS Status finished

Project type is j2se
Comment 7 Maros Sandor 2006-07-12 09:00:17 UTC
I assume you use CVSNT. Make sure that CVSNT locking service is started (in
Control panel, Administrative Tools, Services).
Comment 8 Peter Pis 2006-07-12 09:01:33 UTC
>:local:C:\...
This is a problem (back-slashes) for javacvs client. If you want to use :local:
connection successfully with new Netbeans CVS support you have to install CVSNT
server. (:local:/path_to_repo)

Please follow steps:
http://www.netbeans.org/kb/faqs/version-control-system.html#FaqHowToAccessLocalCVS

Don't forget to use unix path for repository in CVSROOT field. (Control Panel ->
CVS for NT -> Repository configuration(tab) -> Name (column))
Comment 9 ulfzibis 2006-07-12 14:45:45 UTC
> I assume you use CVSNT. Make sure that CVSNT locking service is 
> started (in Control panel, Administrative Tools, Services).
I don't use CVSNT-Server, but I used cvs.exe as client for the old CVS support.

> >:local:C:\...
> This is a problem (back-slashes) for javacvs client. 
IMHO, this is not really a progress against the old CVS support. Nearly all Java
libraries know to deal with back-slashes. Is there any chance to have this here
also?
Where can I edit CVS repository settings ?
In other words: I miss "Version Manager->Customize".

> If you want to use :local: connection successfully with 
> new Netbeans CVS support you have to install CVSNT server.
This also is not really a progress against the old CVS support. On my
narrow-chested system I'm not amused to spend resources on CVS server.
In my opinion, purpose of local CVS is simplicity and minimal use of resources.

What users want:
1. Install new CVS support (or NB 5.5)
2. Disable old CVS support
3. Continue work without problems
... and if there is a problem, there must be an unmistakable error message like:
"No local repository under new CVS support without running local server"

Comment 10 Maros Sandor 2006-07-12 15:24:43 UTC
You do not have to run local server, just use CVSNT as your cvs command-line
client as described in the faq. You can then access your repository via :local:
method.
As for Versioning manager, we plan to have similar config dialog in the future.