Eclipse vs. CVSNT sserver protocol...

[markus_heiden]

Hi folks,

Eclipse does not support the CVSNT sserver protocol as you may have already sadfully noticed. But there is a plugin which adds CVSNT support to Eclipse:

http://home.arcor.de/rolf_wilms/cvsssl/cvsssl_help.html

This plugin has to be extracted to the Eclipse plugin folder directly.

Settings for Eclipse CSV-View with bots-united CVSNT is attached.

Markus

[Rick]

Nice
Does it need cvnt externally or has it code for sserver build in?

[Pierre-Marie Baty]

I wonder when sserver will become the official CVS protocol...

[Rick]

Originally Posted by Pierre-Marie Baty

I wonder when sserver will become the official CVS protocol...

Never I think. AFAIK work on CVS is kinda stopped. I believe some CVS developers work on Subversion now.

Ugh...and whats so good about sserver? I think only CVSNT supports it, which...isn't my favourite piece of software

[Pierre-Marie Baty]

Weird guys. How can you possibly stop working on something that's become the standard de facto in the industry for concurrent source code versioning to develop an alternative system that no one knows ? Makes little sense for me.

Anyway, nice thing Markus... too bad I don't use Eclipse No problem with your account, by the way ?

[Rick]

Originally Posted by Pierre-Marie Baty

Weird guys. How can you possibly stop working on something that's become the standard de facto in the industry for concurrent source code versioning to develop an alternative system that no one knows ? Makes little sense for me.

Hmm seems I was wrong: http://ximbiot.com/cvs/wiki/index.ph...Current_events
Some recent updates there...

My guess is that just a few CVS guys started their own project. Oh and SVN is fairly known (in the OS community atleast). The KDE team even switched to it from cvs and I use it for my new project

[markus_heiden]

My account works fine, thanks!

Cvsnt is not needed for the plugin.

Subversion is becomming THE state of the art versioning system, because it don't has the many weaknesses of cvs: e.g. subversion has an api and it has atomic commit, so you can see which files have been changed by each commit and many more. Yet, it is not as easy as with cvs to set a server up, but it is already as easy to use as cvs.

Markus

[Rick]

Originally Posted by markus_heiden

Cvsnt is not needed for the plugin.

Cool

Originally Posted by markus_heiden

Subversion is becomming THE state of the art versioning system, because it don't has the many weaknesses of cvs: e.g. subversion has an api and it has atomic commit, so you can see which files have been changed by each commit and many more. Yet, it is not as easy as with cvs to set a server up, but it is already as easy to use as cvs.
Markus

Agreed
Its much faster as well, also for some reason it feels 'less hacky' than CVS.

A downside is, that the .svn directories seem to be bigger than their .CVS counterparts.