Problem Using Nested Packages in SVN

[Richard Seroter]

Hi,

Using version 7.0.816 of EA, and when I build a complicated, nested model structure, and add each package individually to my source control system (SVN), everything seems ok.  However, when I try and pull the model down fresh, I only get the stubs.  Now, I have the checkbox selected to only stub the child package, but, if I choose "Get Latest", I'm told that the stub isn't connected to the source control system!  

That is, it seems that the nested model package pulled from SVN isn't keeping it's source control settings.  If I turn off the "nested stubs" option in the "Version Control Settings" panel, then a "get all latest" pulls the whole tree, BUT, the nested packages are presented without their source control hooks.

Is there a known issue with checking in deeply nested EA model into source control systems?  

[Richard Seroter]

Finally figured it out.

The Version Control unique ID set up during initial configuration is embedded in the XMI files, and thus all folks who pull down the EA model from SVN must make sure they use the exact same configuration ID.

[«Midnight»]

Excellent advice Richard!

Thanks for posting back so the rest of us will know what to do.

David