Just ran into this issue when trying to run Maven tests on one of our modules.
Looks like due to a bug in the latest Java OpenJDK release:
Following one of the suggests in the above post, I added this flag to the surefire configuration and it did appear to resolve the issue:
-Djdk.net.URLClassPath.disableClassPathURLCheck=true
for example, see:
fyi @dkayiwa it looks like you may have run into this with the REST module today.