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.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|2d 16m||1||Olivier Lamy (*$^¨%`£)||04/Sep/09 16:23|
|Workflow||jira [ 12963958 ]||Default workflow, editable Closed status [ 13000497 ]|
|Project Import||Mon Apr 06 01:15:59 UTC 2015 [ 1428282959282 ]|
|Patch Submitted||Yes [ 10763 ]|
|Flags||Patch [ 10430 ]|
|Workflow||jira [ 12726127 ]||Default workflow, editable Closed status [ 12764441 ]|
|Project Import||Sun Apr 05 13:14:21 UTC 2015 [ 1428239661755 ]|
|Resolution||Duplicate [ 3 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Fix Version/s||maven-shared-jar-1.1 [ 15654 ]|
|Assignee||Olivier Lamy [ olamy ]|
|Component/s||maven-shared-jar [ 13279 ]|