Author Topic: EA - ClearCase Integration (Read 4606 times)

pH · « **on:** January 15, 2009, 11:35:34 pm »

Hi,

The version control section on website says it is possible to integrate with ClearCase Configuratoin Management System. But there is not enough material on the internet or in the help similar to what we have for SVN. Is there any material available that explains how EA can be integrated with ClearCase ?

Thanks,
pH

Dorian Workman · « **Reply #1 on:** January 16, 2009, 08:10:19 am »

Clear Case is SCC compliant. Follow the instructions in the Help and in the Version Control whitepaper for SCC Configuration. We have set it up and it works great.

pH · « **Reply #2 on:** January 16, 2009, 11:27:30 pm »

Thank you. Its working for me.

-pH

Dorian Workman · « **Reply #3 on:** January 17, 2009, 03:40:43 am »

Good stuff.

pH · « **Reply #4 on:** January 21, 2009, 12:32:38 am »

Hi,

Whats the mechanism by which EA stores the files into Configuration Management. It creates 16 folders from ea0 to eaF and then lot of xml files inside that with its own naming convention. Is it possible to change this naming convention? If not is there any mechanism by which I can know which xml corresponds to what package in my EA Model.

Thanks,
pH

mrf · « **Reply #5 on:** January 21, 2009, 09:56:01 am »

There are quite a few reasons why we came to the current naming system.

1. Naming package XMI files by their package name would not ensure uniqueness (either within the project itself or across any number of the projects the repository may store. As a result the last 12 digits of the package's GUID (globally unique identifier) are used to name the file.

2. Windows has a hard limit on the number of files that can be stored in a directory (and yes people were hitting it

). As a result we split the version control repository up into 16 seperate directories, allowing for more files to be stored. The directory a file is placed in is worked out by the first character of it's file name.

While one may argue that the system isn't easy to manually trace, the system was designed for EA to automatically manage the version control and to ensure package XMI uniqueness, not for human readability.

You can identify a certain package's corresponding XMI file by right clicking on the package and selecting Package Control | Configure from the context menu. The corresponding XMI file is displayed in the XMI File Name field

pH · « **Reply #6 on:** January 27, 2009, 06:35:28 pm »

Hi,

Is it possible to create a separate branch in clearcase through EA?. It seems to be using the main branch by default.

Thanks,
pH

Sparx Systems Forum

News: