Set up Subversion

Return to Introduction  Previous page  Next page

Obtaining and Installing Subversion

Note: 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.  Enterprise Architect does not work with Subversion releases earlier than Subversion 1.2.

Before Enterprise Architect can be used with Subversion, the appropriate software must be installed by a Subversion administrator. Ask your system administrator to obtain and install the Subversion server and client applications.

Official Subversion documentation can be found at:, while executable files for Subversion can be obtained from:

You require the Windows executables for your client machines running Enterprise Architect in the windows environment. If you plan to run your Subversion server on a non-windows platform, you must download a binary suitable for that platform as well. 

Chapter 6 in the Subversion documentation provides guidance on how to configure the server for different methods of access by the client.  Secure connection methods are also covered in this chapter.

Your administrator should set up userIDs and passwords for everybody that is to access the repository.  Your administrator should then provide all users with the path to the repository, and ensure that they can all connect. 

Before users can make use of Subversion, they must create local working copies from the repository by checking-out a repository sub-tree.

Steps for setting up a repository and creating a local working copy can be found at:

Note: We 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.

Repository URLs

Subversion repositories can be accessed using many different methods, on local disk or through various network protocols. A repository location, however, is always a URL. The table below describes how different URL schemas map to the available access methods.


Access Method


Direct repository access (on local disk)


Access via WebDAV protocol to a Subversion-aware Apache server.


Same as http://, but with SSL encryption.


Access via custom protocol to an svnserve server


Same as svn://, but through an SSH tunnel.

For more information on how Subversion parses URLs, see

See Also