Closed tferr closed 2 years ago
The error is innocuous in that the try/catch is inside the for loop, therefore, it tests each jar file (aka a zip file) independently. Regardless of a jar file being invalid, the method ClassUtil.findAllClasses
will succeed.
Most likely what happened: you were still running a mvn build and one jar file was a .part file or something, still empty.
Just got this exception while fiddling with the editor. Unfortunately, I don't have a step-by-step procedure to reproduce it.
(pinging @acardona)