Migrating shadow packages to other shadow packages in UML models

When you migrate a shadow package to another shadow package, you redirect the reference from one shadow package to another shadow package, which becomes a shared model in a separate project.

About this task

Typically, you migrate a shadow package when multiple models share a common package. Otherwise, you can experience memory issues if every model that references the shadow package must import it. Other benefits to this approach include that you can work with a model at a component level instead of an entire project, and that fewer dependencies exist.

Before you migrate a shadow package to another shadow package, you might want to create a model from the shadow package to isolate the shadow package to migrate to. For more information, see the related topic about creating a model from a shadow package.

To migrate a shadow package to another shadow package:

Procedure

  1. Right-click the shadow package that you want to redirect to another shadow package; then click Migrate Shadow Package.
  2. In the Migrate Shadow Package window, select the common shadow package to which to redirect the reference.
  3. Click OK.
  4. To complete the migration, in the Migrate Shadow Package window, click OK.

What to do next

The reference that you selected now points to the shadow package in the core or common project; duplicate shadow packages are not an issue because only one common package exists in the workspace.

Feedback