Community
Participate
Working Groups
Hello, It seems that CVSNT is not well supported with TeamCVS. Could it be possible to make Eclipse compliant with CVSNT 2.0.0 (the latest release)? Is it possible to put this request to a high priority? regards Xavier
There are a couple of reasons for the lack of support for CVSNT. 1) The older versions (1.11.1.1 and 1.11.1.2) have some bugs that effect some Eclipse CVS functionality. However, the number of bugs is small so these versions are usable. 2) The newer versions (1.11.1.3 build xx) are highly unstable with some builds working great and other builds failing miserably. I haven't yet tried 2.0.0 so I can't say how well it works. 3) We don't use CVSNT regularly and we don't test against it (due to above reasons and manpower available) So, what is required is an organization (or person) to come forward and commit to providing support for CVSNT and Eclipse. If such a party did come foreward, we would be happy to provide whatever support we can on the Eclipse side.
Rather than raising a new bug (can't find an existing one) I'm adding to this for current CVSNT/Eclipse issues. We (the cvsnt dev team) are currently in discussions with Mike Milinkovich over this to fairly allocate manpower to sort out any remaining issues. The recent issues I know of are: 1. Case sensitivity on drive letters - fixed in 2.0.51/2.0.56. You always get back the same root that's defined on the server, so eclipse shouldn't see anything unexpected. If there are any outstanding issues with this it'll need looking at. 2. The 'repository prefix is enabled' dialog. This really is obnoxious and should go. It stops cvsnt on Unix from being used with eclipse at all (Unix has no drive letters). All cvsnt repositories are now virtual and there's no concept of a prefix to disable (it's strongly recommented *not* to use drive letters as it affects cross-platform compatibility). There's also the issue of cvsnt enhancements which can be addressed at a later date - my own priority is helping the user experience and getting cvsnt to some level of 'supported'.
Tony, Our only issue with repository prefixes was that, in older versions of CVSNT, when they were enabled, file paths in text messages still used the full path. This broke the advanced CVS features in Eclipse (e.g. syncing). If this is no longer the case in the latest versions of CVSNT, then we can remove the message, although we may want to detect the CVSNT version so we can let users know that they should upgrade if using an older version. As for having CVSNT supported by Eclipse, our position has always been that if someone offers to provide support for it, we are willing to say it is supported. By providing support, we mean handling all the bugs related to CVSNT as well as performing tests (both manual and automatic) when new Eclipse builds and CVSNT builds are produced. If you are willing to commit to this, then I would be glad to say that CVSNT is supported in Eclipse.
Tony, would it be possible to structure the CVSNT project to have stable and development streams for the server? We can test against the stable stream and indicate that the latest stable is supported. We expect stable streams to make no changes to the protocol messages. This is currently how the CVS project manages development, and works well with tools that need to test against a stable release. We will remove the message for 3.0 M3, and run some tests. What version of CVSNT is the latest stable? Which one should we be testing against?
Adding Tony to the CC list - it's the best way to track changes.
The latest stable is the commercially supported one downloadable from http://www.cvsnt.com. The latest unstable is usually downloadable from http://www.cvsnt.org/wiki/Download. Stable releases are typically every 3 months. Unstable releases are typically weekly. It's unusual for any changes to affect frontends, although of course they miss out on any new features. There are also service releases that come out to fix post-release bugs. These are only to fix/clarify things rather than to add features. The latest version is 2.0.58 which was released a few days ago. I can't really test eclipse as I'm not a java programmer and haven't the faintest idea how to use it (there's also the problem of time). That really needs an extra person who uses both to do that kind of testing. The problem I usually have is that users say eclipse doesn't work by saying things like 'it won't sync' whereas I really want things like what command was issued, what was supposed to happen, and what actually happened. Is there a way to get this information? (something like 'eclipse command: cvs -q update -dP, expected response: blah, got response: blahblah' in a file that the user can send to me. A client/server trace would be nice too).
We always point people to an entry in our CVS FAQ that will give output similar to the CVS_CLIENT_LOG. This makes it pretty easy to see what information was sent back and forth. Here's a link to the entry: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm- home/docs/online/cvs_features2.0/cvs-faq.html#misc_0
Thanks, that'll help a lot if I can get that detail.
I have removed the CVSNT specific messages from the Eclipse CVS plugin.
verified, no more log message and I've sniff tested the CVS plug-in against - cvsnt 2.0.58
