Book a Demo

Author Topic: How to make source import location flexible  (Read 2610 times)

Joel Rosi-Schwartz

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
How to make source import location flexible
« on: October 10, 2008, 02:24:45 am »
Hi,

I am trying to figure out how to make the location of a Imported Source Directory adjustable so that different developers who share the model can have the source located in different locations. I have looked into Local Paths, but as far as I can tell this is not supported for imported source.

Is there a way to accomplish what I need to do?

I am using EA 7.08

Thanks,
Joel

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: How to make source import location flexible
« Reply #1 on: October 10, 2008, 10:22:35 am »
Local paths are only used for class source code.  It is exactly what you need.

Joel Rosi-Schwartz

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: How to make source import location flexible
« Reply #2 on: October 10, 2008, 11:01:08 pm »
Quote
Local paths are only used for class source code.  It is exactly what you need.

I guess I was not clear enough so allow me to specify a scenario.

A team as several developers and there is no policy on where the developers keep their projects. In fact to make things even more interesting in some cases the drive (C:, D:, H:, Z:, etc.) differs per user.

Tom keeps his projects on D:\projects, while Bill has his on H:/bill/projects and Sue has her's on Z:\Uers\sue\projects.

Tom does the initial reverse engineering, but later Sue want to update the model be synchronising from the code base into the model, i.e. reimporting to pick up new and changed code.

Can this be accomplished with Local Paths and if so how?

Thanks,
Joel



Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: How to make source import location flexible
« Reply #3 on: October 13, 2008, 08:07:29 am »
Tom sets the local path "Projects" to point to D:\projects.
Bill sets the local path "Projects" to point to H:\bill\projects.
Sue sets the local path "Projects" to point to Z:\Uers\sue\projects.

From that point on, any code imported below any of those branches will be under something like %Projects%\Project1\MyClass.cs.

If people have already importing code before setting up the local path, just click the 'Apply Path' button on the local paths dialog.