SigTest currently will not process a "facade jar" where that "facade jar" does not contain any classes but instead contains a manifest file (e.g. META-INF/MANIFEST.MF) which in turn references other jar files in its "Class-Path" entry.

We have encountered a case where weblogic.jar (which is a facade jar) that contains no classes but references many jars. And the list of jars seems to be changing somewhat frequently. We are finding it cumbersome to unzip these manifest files and track down their referenced jar files to include them on our sigTestClasspath.

To be clear, this is not a bug but would be a nice ease-of-use feature for the next major version of sigtest 4.0