Create a Subversion Environment

Before Subversion can be used as a version control provider for Enterprise Architect, the appropriate software must be installed and configured by a Subversion 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 Subversion environment.

Topics

Topic

Detail

See also

Install server components

Executable files for Subversion can be obtained from the Apache Software Foundation.

Subversion server components are available to run on a wide range of different hardware and operating systems; Enterprise Architect is not affected by your choice of server components.

VisualSVN is a package that can greatly simplify the installation, configuration and management of your Subversion server.

 

Apache Subversion

Official Subversion Documentation

Create a repository

Please consult the official Subversion documentation.

Official Subversion Documentation

 

Create Subversion users

Please consult the official Subversion documentation.

Official Subversion Documentation

 

Create a new repository sub-tree

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 sub-tree in Subversion for each new Enterprise Architect model.

TortoiseSVN can greatly simplify the process of creating new repository sub-trees.

 

Create a Repository Sub-tree

Install client components

Executable files for Subversion can be obtained from the Apache Software Foundation.

 

Apache Subversion

Create a working copy folder

To create a local working copy, you must perform an initial check-out of a folder from the Subversion repository; this downloads a copy of the folder and its contents, to create your local working copy.

TortoiseSVN can greatly simplify the initial check out of a working copy folder.

 

Create a Local Working Copy

Subversion under Wine/CrossOver

The set up and use of Subversion with Enterprise Architect under Wine is almost identical to when running natively under Windows, apart from some minor differences when installing the Subversion client and performing the initial check out of the working copy folder.

 

Subversion under Wine

TortoiseSVN

TortoiseSVN is a Windows shell extension; Enterprise Architect can not use TortoiseSVN as its client, it must use the Subversion command line client.

 

TortoiseSVN

Notes

Enterprise Architect relies on exclusive file locking when applying version control to its packages; file locking was not introduced into Subversion until version 1.2, therefore Enterprise Architect does not work with Subversion releases earlier than Subversion 1.2
Sparx Systems recommend that each new Enterprise Architect model being added to version control with Subversion should have a separate repository sub-tree created for it, and users should create a new local working copy from the sub-tree to be used with that model