Caching of hardcoded paths can cause issues

[maxandersen]

Describe the bug
recently something changed in caching so if you have a change in your ~/.m2 settings/location between builds the build fails with errors like:

ava.lang.RuntimeException: java.lang.RuntimeException: java.io.UncheckedIOException: Error while reading file as JAR: C:\Users\max\.m2\repository\commons-io\commons-io\2.6\commons-io-2.6.jar
Caused by: java.lang.RuntimeException: java.io.UncheckedIOException: Error while reading file as JAR: C:\Users\max\.m2\repository\commons-io\commons-io\2.6\commons-io-2.6.jar
Caused by: java.io.UncheckedIOException: Error while reading file as JAR: C:\Users\max\.m2\repository\commons-io\commons-io\2.6\commons-io-2.6.jar
Caused by: java.nio.file.NoSuchFileException: C:\Users\max\.m2\repository\commons-io\commons-io\2.6\commons-io-2.6.jar

Expected behavior
in this case its due to doing a build on windows and then afterwards on linux - both have a functioning ~/.m2 folder but since we now store absolute paths things goes wrong.

similar could happen if you cleaned your ~/.m2 repo or changed your .settings.xml or similar