Nested packages and version control

[Stolperwurm]

Hi,

I have a project with some packages under version control, nested in a single package which is under version control as well.

I try to get this structure on another computer as described in http://www.sparxsystems.com/enterprise_architect_user_guide/projects_and_teams/usingnestedversioncontrolp.html: "... if you check out or get a version controlled package with nested packages not already in your model, you see stubs in the model for the nested packages only. If you select the Get All Latest option from the version control menu, Enterprise Architect populates these new stubs from the version control system".

What I do is getting the highest level package by "Get Package...". I see then my packages structure, all packages show the "under version control an not checked out to me" symbol. Then I select the "Get All Latest" option. What I get is just a popup titled "EA" and the following message: "The following packages currently have no connection to version control and can not be updated: <list of all the nested packages>".

I look at the "package control options" dialog of the nested packages and see that everything seems to be okay except the parameter "version control": its value is "(None)". This parameter is not selectable unless I check out the "main" package.

Isn't it possible that I just use the "Get All Latest" option without any further actions?  

I work with EA 8.0, Clearcase 7.0, Win XP SP3.

Best regards
Stolperwurm

[Frank Horn]

Could it be that the nested packages have another version control configuration than the top level package, and that only the top level package's configuration is defined for the target model?

You would have to use the global version control configuration (context menu "Package Control - Version Control Settings..." on any package, e.g. on the model root) to see if all configurations are there in the "Defined Configurations" list at the bottom.

[Stolperwurm]

Hi Frank,

thank you for your quick reply.

Could it be that the nested packages have another version control configuration than the top level package...

No, all the packages have the same version control configuration. But anyhow, your idea led me to a solution: in the failing case (Oct 29th) I setup the "Version Control Settings" on the importing computer with an own "Unique ID", different from the one on the exporting computer. Now I input on the importing computer the same name as I chose on the exporting one and everything works well.

I found out as well that even the path selected by the "Select Path..." button in the "Version Contol Settings" must be exactly the same on the importing as on the exporting computer (at first I selected a subpath which contained anyhow each of the XMIs to be imported).

It seems that importing nested packages from version control works well only if

• I input the right "Unique ID",
• I select the right path.

Is that right?

Best regards

[Frank Horn]

You can have different absolute paths on different machines, but for each controlled package you need the same relative path on every machine to the local working copy root path associated with the "Unique ID" on the respective machine.