I have mentioned this to Paul. Clearly the tests run by mvn are not picking up the url handler protocol packages as vfs* urls are not being recognized. I create this isse for Paul to look into why this is:
Paul thinks this could be due to the following jdk bug:
We don't put the vfs into the system class loader when running the server or under eclipse so I don't see that this directly applies. Since the bug is old, it could be that the handlers must be int he application class loader and mvn test harness is creating a child class loader of that, and the handlers are only visible from the thread context class loader, and so some form of this bug applies.
We need to see what class loaders exist when the first call to resolve a vfs* url is made. This will require hacking the jdk source and running with -Xboostrap/p:/path-to-jdk-source-classes to override the handler loading code.
The problem went away when I added
to the maven surefire plugin configuration.
More info here: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html
The change doesn't seem to break anything, so I think it's ok. There is still one test failure and one error, but they are happening when running from eclipse also.