Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Create a CVS Environment
Before CVS can be used as a version control provider for Enterprise Architect, the appropriate software must be installed and configured by a CVS administrator.
The following topics describe some basic tasks that must be completed and some tools for performing these tasks, in order to create an operational CVS environment.
Topics
Topic |
Detail |
See also |
|---|---|---|
Install server components |
Executable files for CVS can be obtained from the Free Software Foundation, or from March Hare Software. CVS server components are available to run on a wide range of different hardware and operating systems. Enterprise Architect is not affected by you choice of server components.
|
|
Create a repository |
Please consult the CVS documentation.
|
|
Create CVS users |
Please consult the CVS documentation.
|
|
Create a new repository module |
It is good practice to create folders in your PC's file system for organizing your files and documents. Similarly, it is good practice to create a new repository module in CVS for each new Enterprise Architect model. A repository module represents a project, or set of related files in the repository. TortoiseCVS can greatly simplify the process of creating new repository modules.
|
|
Install client components |
Executable files for CVS can be obtained from the Free Software Foundation, or from March Hare Software. Enterprise Architect is a Windows based application - it requires a Windows based CVS command line client for integration.
|
|
Create a working copy folder |
To create a local working copy, you must perform an initial check-out of a module from the CVS repository. This downloads a copy of the module, to create your local working copy. TortoiseCVS can greatly simplify the initial check out of a working copy folder.
|
|
CVS under Wine/CrossOver |
The set up and use of CVS with Enterprise Architect under Wine is almost identical to when running natively under Windows, apart from some minor differences when installing the CVS client and performing the initial check out of the working copy folder.
|
|
TortoiseCVS |
TortoiseCVS is a Windows shell extension. Enterprise Architect can not use TortoiseCVS as its client, it must use the CVS command line client.
|
Notes
| • | If you do not already use CVS for version control, you should consider using Subversion instead. Subversion's client-server protocols provide a broader range of possibilities for connecting to remote servers, with easier set up of secure connections |
| • | Sparx Systems recommend that each new Enterprise Architect model being added to version control with CVS should have a separate repository module created for it, and users should create a new local working copy from the module to be used with that model |
