[news.eclipse.tools] Re: Release to CVS is not working

[James Moody <James_Moody@xxxxxxx>]

Pierre wrote:
> I have been trying the 14 feb build to see if CVS integration was working 
> better for me. This time it synchronize alright with the cvs repository. 
> Great !
>
> Everything was working nicely until I try a "Release" for just one class. 
> Then, the ide hangs forever (after showing me a nice comparision between my 
> file and the current cvs version). After 15 min, I decided to cancel the 
> operation. I cannot affort waiting that long for each "commit" to cvs.

This is definitely unexpected. We use cvs support here on a daily basis 
and release is usually < 2 sec for a single class, depending on the 
size. Was the repository a local machine, or somewhere on the Internet?

Most importantly, are you using the old VCM codebase or the new 2.0 Team 
codebase? If you don't know, you're probably using the (default) VCM 
codebase. Starting very soon, our new codebase will replace the old; as 
it is almost a complete rewrite, your problem may very well go away.

It is possible that your problem was just due to a network hiccup! Did 
you try it again? Your results are certainly not typical.

> I will be trying Eclipse very soon again (hopefully with final 2.0 
> release). It is such a nice IDE. But my memory of VisualAge tells me that 
> "synchronization of vaj repository with another versional control system" 
> has always been problematic (kind of 20 min to do a "get latest"...).

On the contrary, CVS is currently our number one priority for 
functionality and performance, and it is the repository that (nearly?) 
all of the Eclipse developers are using. And our new 2.0 Team codebase 
is designed generically in such a way that *any* version control system 
can become a first class citizen in Eclipse, just as CVS is.

Hope you try it again with success!

james