| Prev | Next |
Version Control Settings
Defining Version Control settings within Enterprise Architect should only be performed after you have successfully created the Version Control environment that you intend to use to control your Package files. If you have not yet done so, please refer to the Help topic Applying Version Control in a Team Environment for a summary of what is required.
To set up a Version Control configuration on your model, or update an existing Version Control configuration, you define a number of settings that control how the status of your model is communicated to your Version Control system. You define these settings using the 'Version Control Settings' dialog.
Access
|
Ribbon |
Settings > Version Control > Project-VC |
|
Context Menu |
Right-click on Package > Package Control > Version Control Settings |
Configuration Options
Option |
Action |
See also |
|---|---|---|
|
This model is private |
Select to specify that this model database is to be accessed by just a single user (Private Model). Leave unselected (the default) or deselect to specify that the database is to be accessed by multiple concurrent users (Shared Model). If in doubt, use the default setting. |
Version Control Usage |
|
Save nested Version Controlled Packages to stubs only |
Select to specify that the exported XMI file for a Version Controlled Package will contain Package stubs (place holders) for nested Version Controlled child Packages (recommended). Deselect to specify that the exported XMI file will contain the full content of nested Version Controlled child Packages. |
|
|
For all Packages, create placeholders for external references |
Select to force all XMI 1.1 imports across the model to exclude incoming relationships and instead create external references. If the 'Create placeholders for missing External References during XMI 1.1/2.1 and Native File Import' checkbox is not selected in the XML Specifications options for a user, this field overrides that setting. The XML Specifications Help topic provides an example of the benefits of selecting this option. |
XML Specifications |
|
Unique ID |
Specify a name that uniquely identifies the configuration. Either:
|
|
|
Type |
Click on the appropriate radio button for the type of Version Control system you are associating with this configuration. The middle section of the dialog changes to display a collection of fields relating to the type of Version Control configuration you are defining. Set the type to SCC for:
For any other product that you are using, select the type that matches the product - CVS, Subversion or TFS. |
SCC Settings CVS Settings SVN Settings TFS Settings |
|
New |
Click on this button to clear the fields and create a new Version Control configuration. |
|
|
Save |
Click on this button to save the details of a new or updated configuration. |
|
|
Delete |
Click on an entry in the Defined Configurations list and click this button to remove the definition of the selected configuration from this model. |
|
|
Defined Configurations |
Review a list of configurations that are in use in the current model. |
|
|
In future, do not prompt for incomplete configurations |
Select to specify that the user is not prompted to complete the definition of configurations that are not fully specified (the default). Deselect to prompt the user to complete configurations that are not fully defined. |
|
|
Close |
Close the 'Version Control Settings' dialog. |
|
|
Help |
Display this Help topic. |
Notes
- It is important that, for any given Version Controlled Package file, any user accessing that file from any model uses Version Control configurations having the same Unique ID
- When you first open a model that was created by another user and that uses Version Control, the Version Control configuration(s) used by that model do not yet exist in your Windows registry settings; you have to complete the definitions of those configurations before you can use Version Control in that project
- If User Security is enabled, you must have 'Configure Version Control' permission to set up Version Control options for the current model
- It is possible to use multiple Version Control configurations in the same model