Version Control
Within Enterprise Architect, you can manage changes to and revisions of your projects by placing individual model packages, view nodes or root nodes under version control. Version control provides numerous key facilities, including:
| • | Saving a history of changes to packages |
| • | The ability to retrieve previous revisions of packages |
| • | Propagating model updates between team members |
| • | Coordinating the sharing of packages between team members
|
You apply version control through a third-party source-code control application that manages access to and stores revisions of the controlled packages. Once the version control software has been installed and configured, you must define a Version Control Configuration within your project. You can then use version control to manage changes to the packages of your model.
Notes
| • | Sparx Systems strongly urge you not to manipulate version controlled package files outside of Enterprise Architect; it is possible to leave the package files in a state that Enterprise Architect cannot recognize |
| • | Database replication should not be combined with version controlled packages |
| • | If the packages under version control contain any alternative images and those images are subject to frequent change, you can set the Export alternate images option on the Options dialog to export the images to the version control repository when you check in the packages; if the images are not subject to frequent change, do not select this option and instead use Export / Import Reference Data to manage alternative images |
Learn more
The material ("material" includes all pages, documents and on-line graphics) on this web site is protected by copyright law. (C) 1998-2013 Sparx Systems Pty Ltd.
