Author Topic: Referencing other EAP projects  (Read 2130 times)

MikiNanuk

  • EA Novice
  • *
  • Posts: 18
  • Karma: +0/-0
    • View Profile
Referencing other EAP projects
« on: July 27, 2004, 09:46:00 am »
We are creating one EAP file for each namespace, so that multiple designers can each work on their own area.  Is it possible for one EAP file to reference another one, so that the classes in the referenced EAP file are available?

For example, we have Company.Product.BizObj that defines basic business objects such as Customer, Account, etc.  Another namespace, Company.Product.Settlement, implements classes that know how to settle an account for a customer, and it would be nice for Settlement.EAP to be able to make use of (but not change) classes defined in BizObj.EAP.

Eric

TrtnJohn

  • EA User
  • **
  • Posts: 176
  • Karma: +0/-0
    • View Profile
Re: Referencing other EAP projects
« Reply #1 on: July 27, 2004, 01:02:45 pm »
Why don't you just use one file with different packages?  You can use source control with each package to prevent multiple users from editing the same package.