In corner cases, VFS loading may fail totally due to webdav provider loading issues.
One corner case reported by Xeno Amess :
- The (a) webdav4(s) file system providers requires (b) jackrabbit-webdav jar, which requires (c) httpclient4 library.
- The standard providers.xml checks classes from (b) and (c) only, so if (a) doesn't exist in the system, the VFS core library fails to load itself.
For example, the reporter found out that versions-maven-plugin pulls in (b) and (c).
So, when the VFS core is only used in their system, it just fails because it does not have (a).
- A workaround is to just install commons-vfs2-jackrabbit* jar as well in the system.
It would be cleaner if the standard providers.xml checked a class in (a) as well, to avoid this kind of problems.