Hi Falko, Unfortunately, I've tried disabling the modulePath ... that didn't seem to disable this behavior and it continues to use the module path.
Also tried all sorts of classloaders, that I knew ... none of them worked. So, I even started adding module-info.java to my src/test/java to open the directory with the test resources. Then the compiler won't compile it unless I add a module-info.java to the src/main/java part ... but if I also do that IntelliJ no longer likes any maven modules that would access that jar ... geee ... I think today I'll be doing some deep classloading debugging. Was just hoping for a simple solution, but I guess there isn't. Chris -----Original Message----- From: Falko Modler <f.mod...@gmx.net> Sent: Freitag, 28. Januar 2022 01:07 To: users@maven.apache.org Subject: RE: Problems with the maven-failsafe-plugin and loading of resources from (test-)jars Hi Christofer, you might want to try disabling https://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#useModulePath You could also try to use the TCCL instead (Thread.currentThread().getContextClassloader()). Cheers, Falko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
