BorlandTalk.com

OBones · Guest

Hi all,

The Jedi Visual Component Library (JVCL) has changed its developer
repository from CVS to Subversion (SVN).
This follows the change already made by the Jedi Code Library (JCL) and
the repeatdly poor quality of service anonymous users were getting out
of the CVS services at SourceForge.
This new version control system has many advantages over CVS and some
new functionalities that will help further development (this comparison
is developed in the Subversion book that can be freely read at
http://svnbook.red-bean.com/).
All active developers of the Jedi Visual Component Library should
migrate to this new system. This process was announced and prepared
during the past few weeks in the developer forums
(news://forums.talkto.net/jedi.vcl).
As you have probably noticed in the JVCL homepage on Sourceforge
(http://sourceforge.net/projects/jvcl), the “subversion” tab appeared,
this page containing information to connect to the SVN repository and to
browse its content from a web browser. Information specific to the JCL
and JVCL repositories is also available on the project Jedi Wiki here:
http://homepages.borland.com/jedi/wiki/index.php?title=Repository

Starting today, the latest sources of the JVCL will only be present in
the SVN repository, the CVS repository will be kept read-only for
courtesy purposes, changes made in the SVN repository will NOT be
replicated into the CVS repository.
All users who want to have access to the latest sources should use
Subversion. For Windows users, TortoiseSVN
(http://tortoisesvn.sourceforge.net/) is a shell integration very
similar and as easy to use as TortoiseCVS.

Starting tomorrow, the daily zips of the JVCL developer repository,
which can be downloaded from http://jvcl.sourceforge.net/daily/, will
now contain a daily snapshot of the Subversion repository.

Should you need help with this, please ask your questions on our
newsgroups at news://forums.talkto.net/jedi.vcl

Regards,

Olivier Sannier
JVCL Coordinator