Dependency Management allows users to include plug-ins in the build path without adding references to the Manifest. By using this mechanism to include plug-ins in the build path, users can compile and develop their code with the convenient features of Eclipse JDT. You can configure Dependency Management to help identify and add new package dependencies from your project's Java code.
It is important to note that this mechanism requires the developer to use the project's Target Definition or the table in the Automated Management of Dependencies section of the Manifest Editor to represent the project's plug-in dependencies. Plug-ins that are placed on the Java Build Path through the project's Java properties page will not be handled by this mechanism.
Manifest package dependencies are automatically managed for Client Services projects by default. This capability can be disabled through the new project wizard when creating a Client Services project and through the Client Services properties tab of an existing project. When enabled, this option automatically updates the Require-Bundle
entries in the project's manifest file based on changes in the project's Java code. The header to which the dependencies are added is specified by a per project preference. You can change this preference on the Dependencies Page of the Plug-in Manifest Editor, the project's Client Services property page under the options tab, or the first page of the Client Services Project creation wizard.
When new package dependencies are added to the project's Java code, the manifest file is automatically updated with the proper entries.
If this option is disabled, the tools will flag the manifest file with error markers if packages are used in the Java code without being referenced in the manifest file. These errors can then be selectively fixed through the quick fix mechanism.
Lotus® Expeditor Toolkit will search for manifest package dependencies by default. This capability can be disabled through the new project wizard when creating a Client Services project and through the Client Services properties tab of an existing project. If this option is disabled, the user can still manually search the project for manifest dependencies by using the Add dependencies
link in the Automated Management of Dependencies panel on the Dependencies page of the Plug-in Manifest Editor.
Parent topic: Client Services project dependencies: XPD622