Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
Patch
Description
A corrupted jar file in the repository, or an attempt to use classes directory in place of a jar during a build is tricky do diagnose, because the exception message does not reveal which file could not been opened.
The attached patch includes the pathname in the exception message.
JarAnalyzerTest was enhanced accordingly.
Attachments
Attachments
Issue Links
- relates to
-
MSHARED-87 ZipException throw by SDK's JarFile constructor may lack file name
- Closed