Managing Project Dependencies

Projects have dependencies on other projects when entities in one project reference entities in a different project. For example, an application project might reference data elements defined in a common model project.

If you configure a project to reference content in other projects without declaring project dependencies, Design Studio creates an error or a warning, depending on how you configured the diagnostic level. Design Studio filters data that appears in dialog boxes and views based on project dependencies.

To manage project dependencies:

From the Studio Projects view, double-click a Project entity to open the entity in the Project editor.
Click the Dependency tab.
Click Add.

The Project Selection dialog box appears.
Select dependencies to add to the dependency list, and click OK.

To locate a specific project in a list of existing project dependencies, enter a partial or full project name in the search field.
From the project dependencies list, select a project and do the following:
- Select a project and click Move Up or Move Down to change the order of the projects. The order establishes priority when upgrading and deploying projects with dependencies. The lowest project in the dependency hierarchy should appear first.
- Limit the project dependency to a specific range of versions by defining the Minimum Version and Maximum Version for the selected project.
- In the Dependency Type field, define whether a project dependency is required in the Design Studio workspace or in both the workspace and the run-time environment. This field is not available for some types of cartridge projects.
- Click Remove to remove the selected from the dependency list.
In the Dependency Violation Diagnostic Level field, specify whether to generate a warning marker or an error marker when projects reference content in other projects but fail to declare a project dependency.
Click Save.