Explanation | Possible invalid syntax of the extension list or specification version attributes. |
Action | Correct the syntax of file. |
Explanation | Possible invalid classpath entry in the library classpath field. |
Action | Correct the classpath entry. |
Explanation | Possible invalid syntax of the extension list or specification version attributes. |
Action | Correct the syntax of file. |
Explanation | Possible invalid syntax of the extension list or specification version attributes. |
Action | Correct the syntax of file. |
Explanation | The name and specification version attributes identifying an Installed Optional Package in the MANIFEST.MF file of the shared library are not unique. The name and specifcation version attributes within the former indicated shared library will take precedence over the latter. Note that the indicated shared libraries may be the same, meaning that the conflicting MANIFEST attributes appear within the same shared library. |
Action | Modify the MANIFEST.MF file by specifying the name and specification version attributes for the Installed Optional Package that will uniquely identify it within any shared library. This will allow the system to uniquely resolve any references to it. If the modification cannot be done, ensure that the overriding Installed Optional Package is the version required by your application(s). |
Explanation | Multiple shared libraries match the specified version criteria. The Library Manager will arbitrarily select one of the libraries that match the attributes of the MANIFEST.MF of the specified module. |
Action | Examine the attributes in the MANIFEST.MF files of the module and all optional package libraries. Ensure all attributes are specified and that they allow for a unique match between the MANIFEST.MF file of the identified module and the MANIFEST.MF of the desired optional package library. |