Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 73787 - Moving a branch tag connected to 1.11.1p1 cvs server fails
Summary: Moving a branch tag connected to 1.11.1p1 cvs server fails
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-13 15:01 EDT by Alan Boxall CLA
Modified: 2004-11-08 16:22 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Boxall CLA 2004-09-13 15:01:31 EDT
the cvs rtag command uses the -B option that was introduced in the 1.11.2 
version of cvs.

This causes the older supported cvs server to fail.

See bug 50004 for details on the change to add the -B option.
Comment 1 Michael Valenta CLA 2004-11-08 13:53:10 EST
Marking a WONTFIX as CVs servers should be upgraded to latest 1.11 release for 
important security fixes.
Comment 2 Alan Boxall CLA 2004-11-08 14:41:34 EST
Seems that this is a moving target...

I had our cvs server upgraded to 1.17 and now Eclipse 2.1.2 fails to get the 
contents of a branch, including HEAD in the CVS Repositories view.

I support various levels of my plugins and need to be able to use older 
Eclipse versions to build and test fixes.   

I can't do this using the same server since Eclipse 3.0 doesn't work well with 
older cvs versions and older Eclipse versions like 2.1.2 don't work with newer 
cvs versions. 

Comment 3 Michael Valenta CLA 2004-11-08 15:05:54 EST
I agree that CVS is a moving target and we are doing are best to keep up. As 
for this particular bug, I felt that the amount of work required to fix the 
backwards compatibility issue was not worth the effort given that most people 
have moved to a newer version of CVS. Evem moving forward to 1.11.2 would fix 
your problem and provide compatibility with all versions of Eclipse.

As for the latest CVS versions, Eclipse 2.1.3 is compatible with 1.11.17. If 
you need to use Eclipse 2.1.2, you can get patches to make it work with 
1.11.17 in bug 46655. 
Comment 4 Alan Boxall CLA 2004-11-08 16:22:08 EST
I also work on a plugin that must work in n->n-1/n+1 environments so I can 
sympathize.

It is ok to close this bug.