Book a Demo

Author Topic: Local directories and paths  (Read 3628 times)

heba

  • EA User
  • **
  • Posts: 44
  • Karma: +0/-0
    • View Profile
Local directories and paths
« on: March 05, 2015, 11:14:06 pm »
Hello,

EA provides the possibility to define a local path and assign it to a variable, e.g. define %BRANCH% and assign to /project/branch-1 to be used for packages.

Now, when I'm branching, I branch the eap together with the controlled packages which aren't version controlled but just Xml files.  Afterwards I'd set %BRANCH% to the new branch and I can load+save packages to that branch.

Unfortunately, these variables seem to be global. So if I have more than one branch and change %BRANCH% to /project/branch-2,  EA also exports packages from the first branch here.

Does anyone have a better idea here?  (Changing the branching strategy is not an option. We're branching the whole project per feature.)

Thanks,
Heiko

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Local directories and paths
« Reply #1 on: March 05, 2015, 11:51:30 pm »
Quote
Does anyone have a better idea here?

Yes, don't branch! Branching an EA model (and merging even more so) is the one of the fastest ways to self destruction.

Geert

heba

  • EA User
  • **
  • Posts: 44
  • Karma: +0/-0
    • View Profile
Re: Local directories and paths
« Reply #2 on: March 06, 2015, 08:27:22 pm »
Thanks, but that's not really an option.  

By the way, in the branch I only modify the controlled package. The EAP file is not merged and the controlled package XML is basically only copied back which is why I usually don't get in trouble here  :)

Best would be to have a path relative to the EAP file path but so far I did not find something like this.

-Heiko