Shared Packages, Version Control etc.

[ditlev]

I have a problem with the use of items mentioned in subject.

I have a master EA project holding the application framework package. This package is both version- and package controlled (using VSS). Works fine.

Every week our application framework library is built (new increment).

In order to get the latest framework for development/design/modelling purpose the '.NET Class Library Exporter for EA' is used to reverese engineer the built dll's.

My problem is this.

Elements used in models from a previous build disappear when the new build is imported.

How do I avoid this?

[Sean Kearon]

EA overwrites the package into which you are importing.  So, one option is to import into a seperate package in your model for each build.  

Does that help?

Sean

[ditlev]

Not really since im trying to avoid re-modelling by developer teams.

D