MainDeployer.parseManifestLibraries contains:

try {
[30+ lines of code to validate and load manifest Class-Path jars]
} catch (Exception ignore)
{
log.debug("The manifest entry in "sdi.url" references URL "lib
" which could not be opened, entry ignored");
}

The fact that the underlying exception is not logged can lead to confusion when attempting to diagnose problems with a jar's manifest.mf. Perhaps the exception could be added to the current log statement like:

try {
[30+ lines of code to validate and load manifest Class-Path jars]
} catch (Exception theException)
{
log.debug("The manifest entry in "sdi.url" references URL "lib
" which could not be opened, entry ignored", theException);
}