Book a Demo

Author Topic: Merge of VS Project creates new packages instead of merging old packages  (Read 4081 times)

Eric Beser

  • EA Novice
  • *
  • Posts: 18
  • Karma: +0/-0
    • View Profile
This is version 13 of EA

I have a set of reverse engineered code that i have placed into my class structure, and had created activity charts, test instances, etc from debugging that code.  Now I had to change the repository location on my desktop to fix my disk space issue.  I updated the code repository from Team Services to get the latest code changes, and i went to sync the model to the code changes.

What happened next is that i now have duplicated packages and classes in my structure, because the model did not merge, it created new class entries for the changed code. 

I have sequence charts, etc in my original untouched packages, and the new packages contain the changed code.  This is not my definition of merge.

What did i do wrong?  the only change (other than some functional changes in the classes) was the location of the source code repository. The project did not change, and the class names and packages did not change.

What did i miss?  I set the path variable correctly and had been using that variable to define the root path of my source code. I was only merging from the source.  Why would it create all new packages and duplicate what is in my model.

How can I merge what i have and make sure that the code is correctly pointing to the source, as i have to continue using the debugger to generate sequence charts on this code.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Merge of VS Project creates new packages instead of merging old packages
« Reply #1 on: December 30, 2016, 08:17:40 am »
Reverse engineering uses the source path as part of the key for matching classes during reverse engineering.

To update the paths for all of your classes, use the local paths dialog. (Code | Source Code | Configure | Manage Local Paths)

(See http://www.sparxsystems.com/enterprise_architect_user_guide/13.0/model_domains/localpaths.html)

Fill out the dialog with your old code path, any id and the source language type. Then click 'Apply Path'. The result is that the old path is substituted for the identifier you provided.

Update the path to point to your new path and synchronization will work again. If you don't want to use the path, you can then expand the path and delete it.