The jar utility fails during an indexing attempt if a JAR's Class-Path contains a non-existent file.

I don't think that the JAR file spec says one way or the other whether the Class-Path entries must exist or not. Certainly URLClassLoader tolerates entries which point to missing JARs or directories.

It seems that the indexer should tolerate missing JARs as well, perhaps logging warnings for missing ones?