ELF WP 2 UML repository instruction

Size: px

Start display at page:

Download "ELF WP 2 UML repository instruction"

Candace Young
8 years ago
Views:

1 ELF WP 2 UML repository instruction Author: Magnus Karge Date: 22/12/2014 Version: 1.2

2 Change Summary Version Date Author/Editor Change Summary /08/2013 Magnus Karge First version /10/2013 Magnus Karge Adjusted the document s layout and minor changes in chapter 2, 3, 4 and /12/2014 Magnus Karge Adjustments in chapter 4 with respect to the new structure in the ELF UML repository. Added TortoiseSVN client as an option in chapter 1 and 4. References Ref. Title/Version/Publication Date/Author 2

3 Contents 1 Getting started Get access to the repository Create a local copy of the repository Configure Enterprise Architect Import packages Edit packages

1 Getting started Connecting to the ELF UML repository using EA requires a command line executable SVN client tool such as CollabNet Subversion Command-line Client to be installed on your computer.

4 1 Getting started Connecting to the ELF UML repository using EA requires a command line executable SVN client tool such as CollabNet Subversion Command-line Client to be installed on your computer. The CollabNet client is available at TortoiseSVN is another popular client: Remember to choose the command line client tools in the installation wizard as indicated in the example below. 2 Get access to the repository The access to the ELF-repository is restricted. Please contact Magnus Karge at magnus.karge@kartverket.no in order to get a username and password. He is also the contact person in case you experience any problems setting up the connection. For read-only access you can use username/password: elf. 3 Create a local copy of the repository Create a local copy by a SVN checkout. The ELF repository is available at NOTE The URL is case sensitive! Enter the following command in the directory where you would like to store the local copy: svn co --username <username> The local path can be any existing directory on your local hard disk. In the example below we chose C:\elf_repository. 4

5 5

4 Configure Enterprise Architect Open an EA project where you would like to import the ELF model. Choose then Project Version Control Version Control Settings.

6 4 Configure Enterprise Architect Open an EA project where you would like to import the ELF model. Choose then Project Version Control Version Control Settings. In the case that the Version Control option is not shown, go to the View menu and choose Workspaces and Commands. In the Workspaces and Commands window go to tab Commands, choose Complete and make sure Version Control is activated (see figure below). In Version Control Settings make sure you tick the Save nested version controlled packages to stubs only check box. Use ELF as Unique ID and select Subversion as the type of repository. Specify the Working Copy Path. In order to import the latest content from the main development branch you should choose ELF\trunk within the path into which you have checked out the repository as described in paragraph 3, e.g. C:\elf_repository. Finally you need to specify the Subversion Exe Path, e.g. C:\Program Files\CollabNet\Subversion Client\svn.exe for the CollabNet client or C:\Program Files\TortoiseSVN\bin\svn.exe for the TortoiseSVN client. The figure below shows an example of how the settings could look like. 6

7 Save the settings. 7

5 Import packages Right-click in the Project Browser on the package into which you want to import one or more packages existing in the repository.

8 5 Import packages Right-click in the Project Browser on the package into which you want to import one or more packages existing in the repository. Then select Package Control and Get Package as shown in the figure below. In the next dialog box select the identifier for the version control system, ELF. Then all available UML packages in the repository will appear in the list. You can choose a single package or you can import a template containing the whole structure and all ELF application schemas. In the latter case select ELF Model.xml. Since most of the classes in the ELF schemas are subtypes of classes defined in INSPIRE schemas the repository contains also INSPIRE application schemas. Those will be imported automatically in case you chose the ELF Model.xml template in the previous step. If you decided to import single packages you may repeat the first steps in paragraph 5 and select INSPIRE Consolidated UML Model.xml in order to import INSPIRE model components into your EA project. In order to import the latest version of the models, right-click on a version-controlled package in the Project Browser and select Package Control Get Latest (to update only this package) or Package Control Get All Latest (to update all version-controlled packages in the EA project) in the context menu. 8

9 6 Edit packages If you want to edit a model you need to check out the relevant package in the Project Browser. Right-click on the package, then select Package Control and Check Out as shown in the figure below. Remember to check in the package when the edit session is finished. To check in a package, right-click on it in the Project Browser, select Package Control Check In. In the case you don t want to send changes to the repository select Undo Check Out instead of Check In. Checking in an updated model opens a dialog box where you should enter a comment that summarizes the changes made by you. 9

Beginning with SubclipseSVN

Version 2 July 2007 Beginning with SubclipseSVN A user guide to begin using the Subclipse for source code management on the CropForge collaborative software development site. Copyright International Rice