The JAR dependency editor updates the manifest class path for a utility JAR or module in an enterprise application. The Java™ build path is updated accordingly for the containing project. It also sets the Main-Class attribute of the manifest, which is typically only used for application client modules.
The JAR dependency editor consists of the following pages and sections:
In cases where your module depends on an EJB module that has an EJB client JAR file, you can choose whether you want to depend on the EJB JAR file or the EJB client JAR file. If you select the Use EJB JARs radio button, the table will not show any EJB client JAR files. If you select the Use EJB client JARs radio button, the table will not show any EJB JAR files that have corresponding EJB client JAR files. If you select the Allow both radio button, the table shows EJB JAR files and EJB client JAR files and allows you to select both types.
It should not be necessary to manually edit manifest files in J2EE projects. However, if you choose to manually edit these files, you should be aware of some common limitations from the Manifest Format specification:
For more information, refer to the official Manifest Format specification. The standard Java APIs are used for reading and writing manifest files.
Adding a directory to the MANIFEST.MF file
IWAE0024W The Manifest Class-Path for archive xyz.jar contains an entry, properties, that is not resolveable to a file or module in the EAR: sample...The EJB specification is not explicit on this issue. However, it does suggest that loose files within an EAR are invalid. Currently, this configuration does work in the WebSphere® Application Server, but you should not rely on this configuration working in the future. You can create a Java project and add the property files to a source folder (or the project if the project is the source folder). On the Modules page of the application deployment descriptor editor, you can add this Java project as a Project Utility JAR, then you can run the EAR file in the WebSphere Test Environment. When you export the EAR file, the Java project will automatically be added to a JAR and included in the EAR.