Book a Demo

Author Topic: Compare with Controlled version, added notelinks  (Read 3428 times)

bnils

  • EA Novice
  • *
  • Posts: 17
  • Karma: +0/-0
    • View Profile
Compare with Controlled version, added notelinks
« on: June 30, 2010, 08:20:36 pm »
After configuring the model for version management (SVN), I have the possibility to compare different versions. But, some things (notelinks) seem to have been added internally and hence get listed as different between model and baseline.

1. Is there any way to suppress these (irrelevant?) changes?
2. Will there always be new/modified notelinks between one version and another?

Best regards Björn Nilsson (using EA 8.0.855)
« Last Edit: June 30, 2010, 09:04:26 pm by bnils »

Jim Beck

  • EA User
  • **
  • Posts: 29
  • Karma: +0/-0
    • View Profile
Re: Compare with Controlled version, added notelin
« Reply #1 on: July 03, 2010, 04:48:48 am »
Hello.  We had a small panic about such a problem also.  We create commonly-used, "library" packages that are shared into many user project models via version control (TFS).  Whenever we get the latest version of a shared library package from version control into a user model, EA adds links to our shared packages.  For example, if a class in our user model B uses a class A in the shared package, it will add a link to A intended to indicate that B uses A.  This seems to be so that EA can show dependendencies in both directions without having to search the model over and over.  At first this was disconcerting.

Our answer to this is that we will never edit and check in shared packages from within user models.  We will always edit them in the models in which they were created, where the library classes are isolated from being polluted with this reverse relationship information.  This makes sense.  In this environment EA has no chance to add this derivative information.  In there it can get checked-in in a state of purity.

One might think it would be nice if show differences ignored this, or we could turn this off, but I don't feel strongly about it at all.  It makes sense that only the source of a shared package should be changing it anyway.

I emailed tech support about this at first and sent another one today describing this scheme here after figuring out what was going on.  If their reply indicates anythign different I'll let you know.

Does this make sense to you?

Jim

p.s. By the way there is a new version of EA 8.0.858.  (It behaves the same way as 8.0.855).  You might want to check it out though they changed and added a lot of features!