Configuration management

JEDI VCS is not only a version control system, see it as a configuration management tool as it includes

Version control with plugin possibility in the GUI clients
- Standalone GUI client to manage all kinds of files like documents, spreadsheets etc.
- CodeGear/Borland IDE client with integration into different Win32 CodeGear/Borland products like Delphi (from 5 to 2009), Borland C++Builder (5, 6, 2006 to 2009)
- Console client for automation tasks in Script-/Batchfiles, Buildtools like Finalbuilder
Todo list (integrated in the GUI versions of JVCS)
Milestone manager (integrated in the GUI versions of JVCS)
Diff/Compare tool (jedivcsdiff.exe)
Buildmanagement tool with a COM based plugin possibility (Jvcsmake.exe) to extend it for various kinds of jobs during the Build cycle

Systemarchitecture

fully database driven with support of most of the the common database systems (Oracle, Firebird, MS-SQL, MySQL)
middleware architecture, based on the ICS & Midware components

Different versions of a module (file) are stored in versions/revisions
Basic support of module branches (will be extended in future versions)
Support of traditional locked based version conrol (as long as a user holds a lock on a module it can not be edited by somebody else) or editing without using locks (not recommended)
Support of Labels/Tags
Synchronisation support for a version, a label/tag, to a date
Projecthistorie for checkins/checkouts/gets/add of modules/delete of modules/branches
database driven user-/projectright management (will be extended with roles)
support of all kinds of files like source code, documents, spreadsheets, presentation files, drawings etc.
Incremental snapshot backup possibilities
only Borland IDE client: version resource control, uses list, transparently adding of change historie information into source code
various reports with export possibilities
encrypted Transfer and storage of modules (128bit Blowfish implementation)