Author Topic: Cross-package references and package control  (Read 6978 times)

thovden

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Cross-package references and package control
« on: July 10, 2003, 07:06:41 am »
We have the following situation:

1. Group A controls package A and wants to develop their model independently

2. Group B controls the "master model" that uses package A. Package A is a controlled package in the "master model"

3. Whenever group A releases their model it is exported from their model and imported to the master model.

So far so good. The problem is occurs when Group B wants to reference elements from package A in the "master model". This works fine up until package A is updated and re-imported. At this point all references to "OLD" package A are deleted from the model.

Is there any way to get this working?
« Last Edit: July 10, 2003, 07:07:37 am by thovden »

potterm

  • EA User
  • **
  • Posts: 126
  • Karma: +0/-0
    • View Profile
Re: Cross-package references and package control
« Reply #1 on: July 10, 2003, 08:06:32 am »
When you import the group A package, do you have the "strip GUIDs" option checked?  If so, this will be the cause - i.e. this option instructs EA to generate new "keys" for each item imported rather than using the existing keys from the group A export.

Hope that helps.
regards,
Martin.

thovden

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: Cross-package references and package control
« Reply #2 on: July 10, 2003, 08:17:39 am »
I don't use the strip GUIDs option. EA deletes all package content when doing an import and it seems like it also deletes all references to the elements it deletes. This would make sense for a "normal" delete but also effectively removes all my cross-package references.

potterm

  • EA User
  • **
  • Posts: 126
  • Karma: +0/-0
    • View Profile
Re: Cross-package references and package control
« Reply #3 on: July 10, 2003, 10:48:06 am »
Having played around with this a little I got the same behaviour.  The same happens if diagram links are created (i.e. the linked elements just disappear from your diagrams following the import).  

Sounds like a bug to me.  Suggest you raise a bug report (unless any of the Sparx support people are reading this...)

regards,
Martin.

thovden

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: Cross-package references and package control
« Reply #4 on: July 11, 2003, 01:07:12 am »
Martin,

Thanks for verifying the problem.

Anyone else got a clever way around this? If not I'll submit a bug report.

gsparks

  • EA User
  • **
  • Posts: 325
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Re: Cross-package references and package control
« Reply #5 on: July 22, 2003, 11:59:39 pm »
Hi there,

The problem arises because the controlled package feature assumes currently that all information about a controlled package will be stored and managed within the controlled package. Now this works fine where the package is part of a repository and is being exported and imported for version control or other reasons ... and it is consistently returned to its 'home' location.

The scenario you are discussing here is a different one. It pre-supposes that the package will be used in a number of different models - possibly in totally different ways. And as the controlled package knows nothing about its target destinations or useage, then this problem arises.

I have spent some time looking at this and revised the import process to retain the necessary information during the delete/rebuild phase such that the controlled package can now be used in the manner you describe. EA will keep the cross package connections that the controlled package knows nothing about and relink where the target element still exists in the imported package.

The new behavior would specifically be of value where you have a framework or model fragment that is re-used in multiple models - but kept up to date in one master location only.

This change will be in the EA 3.60 release which is a few weeks away.  I hope it will meet your requirements.

All the best,

Geoff Sparks


thovden

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: Cross-package references and package control
« Reply #6 on: July 23, 2003, 01:02:55 am »
This is exactly what we need. Thanks again for excellent support on an excellent product.

Torgeir

Darren Lock

  • EA User
  • **
  • Posts: 36
  • Karma: +0/-0
    • View Profile
Re: Cross-package references and package control
« Reply #7 on: August 06, 2003, 01:48:30 am »
Geoff,

this is great news :). This is exactly the scenario that I tried to convey some two years ago.

We run with some 20+ models with shared packages across them. The change management process has been quite labour intensive to date. This will be an absolute blessing.

Thanks again and good luck with the 3.60 release.

Darren Lock
United Kingdom

SWO

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: Cross-package references and package control
« Reply #8 on: November 05, 2003, 05:28:27 am »
 ???
Does an anyone know how this work in Version 3.6

Please Help
Thanks