Book a Demo

Author Topic: Synchronize package from code on different worksta  (Read 2698 times)

lbreuss

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Synchronize package from code on different worksta
« on: August 03, 2012, 09:52:05 pm »
Code Engineering, Java.
How do I "refresh" or synchronize packages from code that have been imported by a colleague?

I browsed the .xml files in the local EA directory and saw some references tag="genfile" with an absolute path to the C:/ drive of my colleague.
When I try to synchronize from my local source dir, nothing happens.
When I "Import Source Directory..." and choose "Synchronize existing classes..." it does not update the existing, but creates a new one with the same name alongside... I end up with each class doubled :(

Should I hack the genfile paths in all .xml files?... (Colleague is unvailable for some days.)
thx for any hint, Leo

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Synchronize package from code on different wor
« Reply #1 on: August 06, 2012, 03:27:37 pm »
Leo,

Hacking xml files won't do you any good, since EA stores all model info in the repository database, not in xml files.

So if you need to hack something then you'll need to hack the database.
Furthermore to prevent this issue int he future look into "local paths" in your EA help.

Geert

lbreuss

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Synchronize package from code on different wor
« Reply #2 on: August 06, 2012, 05:04:36 pm »
Thanks, that helped.
We've agreed on an alias name of the respective local path, so synchronizing from code should work now.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Synchronize package from code on different wor
« Reply #3 on: August 07, 2012, 08:47:30 am »
Local Paths can also be used to correct the issue after it comes up. Even if you don't want to continue using local paths after that point.