Use the Module Dependency Editor to declare dependencies for modules, mediation modules, and libraries
When developing and deploying integration applications, you may need to declare dependencies for your modules, mediation modules, and libraries. Use the dependency editor to manage these required resources.
When a new module or library is created, it may not have any dependencies. Using the dependency editor, you can add dependencies on libraries and Java™ projects. For modules and mediation modules, you can also add dependencies on J2EE projects.
Using the dependency editor, you can add dependencies on libraries and Java™ projects. For modules and mediation modules, you can also add dependencies on J2EE projects.
You can add dependencies when you create a new project. Follow these steps to add dependencies for a module, mediation module, or library that already exists in the workspace:
- In the Business Integration view, double-click the Dependencies artifact under the module, mediation module, or library from which you want to add a dependency. The dependency editor opens.
- Depending on what you need to add, expand the Library, Java, or J2EE section in the Dependency editor. You can only add J2EE projects dependencies for modules and mediation modules.
- Click Add to add the library or project.
- In the selection window, click the library or project and click OK to add it as a dependent. In the dependency editor, you should see the resource added to the container.
- Select a newly added Java or J2EE project in the container to see the Deploy with Module setting and, for J2EE projects, the On Build Path setting. You can clear either of these check boxes to remove dependencies. Do not clear the Deploy with Module check box for libraries. See related concepts for more information on dependencies.
