Book a Demo

Author Topic: How to copy and rename a package?  (Read 3191 times)

xevious

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
How to copy and rename a package?
« on: January 30, 2008, 02:24:07 am »
Is there a way to copy a complete package?

In the project browser of Enterprise Architect I created a package containing a UML Model and respective elements.

Is there a way to copy the whole package including all elements in order to reduce modeling effort?
I'd like to copy the package, rename it and - if necessary - the model and the used elements inside it and modify the model and elements like necessary.

As a workaround I tried to export a complete package (succussfull), but it is not possible to reimport the package. EA detects that this package is already present and the import is failing.

Thank you very much for information & Kind Regards
Xevious

thomaskilian

  • Guest
Re: How to copy and rename a package?
« Reply #1 on: January 30, 2008, 02:32:49 am »
On import Strip GUIDs. That works. Another way is to write a transformation which can do a similar job.

xevious

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: How to copy and rename a package?
« Reply #2 on: January 30, 2008, 04:41:11 am »
Thank you very much, that's it!

Kind Regards,
Xevious

Martin Terreni

  • EA User
  • **
  • Posts: 672
  • Karma: +0/-0
  • Sorry, I can't write
    • View Profile
Re: How to copy and rename a package?
« Reply #3 on: January 30, 2008, 06:57:56 am »
I'm not sure that links to elemen external to the package will remain properly.
Recursion definition:
If you don’t understand the definition read "Recursion definition".

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: How to copy and rename a package?
« Reply #4 on: January 30, 2008, 07:25:12 am »
Links will likely work, since these are not stored in the GUID field of schema tables.

However, if the external package is not in your project - this could happen if you copy the package to a new project - you'll start having problems, since the targets of the links cannot be resolved.
No, you can't have it!