Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Manually Locating Model Branch Files
When importing a Model Branch File from version control, sometimes you do not yet have the associated version control configuration saved in the model that is receiving the import. In this situation, it is simpler to manually locate the Model Branch File and let Enterprise Architect derive the details of the configuration from the branch file you select.
Use to
| • | Browse the file system to locate the Model Branch File (.EAB) to import |
| • | Let Enterprise Architect determine the details of the required version control configuration, based on information contained in the Model Branch File |
Access Right Click on a package | Package Control | Import a Model Branch: Find a Model Branch (.EAB) file
How to
Step |
Action |
See also |
1 |
Ensure that you have an operational version control environment that can be accessed by Enterprise Architect and that you have downloaded all of the version controlled package files and the model branch file associated with the model branch to import, into a valid and accessible working copy folder.
|
|
2 |
Choose the package in the Project Browser, into which the model branch is to be imported.
|
|
3 |
Right-click on the package and choose Package Control | Import a Model Branch. The Import VC Model Branch dialog displays.
|
|
4 |
Click on the button Find a Model Branch (.EAB) file. A file selection dialog is displayed.
|
|
5 |
Browse for and select the Model Branch File that represents the model branch to import.
|
|
6 |
Click Open. If the version control configuration referenced by the file is fully defined within the current model, the import commences at this point. Otherwise, Enterprise Architect displays a dialog prompting you to complete the required configuration.
|
|
7 |
Click Yes to proceed with completing the definition of the version control configuration. The Version Control Settings dialog is displayed.
|
|
8 |
Complete the definition of the configuration. (Typically this involves simply specifying the working copy folder.)
|
|
9 |
Click on the Save button. The configuration details are saved. The import of the model branch proceeds.
|
|
Notes
| • | The Import a Model Branch command is only enabled for packages that you (the current user) are able to edit, as the imported model branch is inserted into the model under the selected package |
| • | It is not necessary to have the relevant Version Control Configuration set up within Enterprise Architect before issuing this command - Enterprise Architect prompts you to complete specification of the configuration if necessary |
Learn more
