[jira] [Updated] (VFS-759) WebDAV providers should loaded only when commons-vfs2-jackrabbit* jar available

["Gary D. Gregory (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/VFS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary D. Gregory updated VFS-759:
--------------------------------
    Fix Version/s:     (was: 2.7.0)
                   2.7.1

> WebDAV providers should loaded only when commons-vfs2-jackrabbit* jar available
> -------------------------------------------------------------------------------
>
>                 Key: VFS-759
>                 URL: https://issues.apache.org/jira/browse/VFS-759
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Woonsan Ko
>            Priority: Minor
>             Fix For: 2.7.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In corner cases, VFS loading may fail totally due to webdav provider loading issues.
> One corner case reported by Xeno Amess [1]:
> - 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.
> [1] https://lists.apache.org/thread.html/rbe64575979ef5f6a677e301d109dbea81c81ba82db556128fe917986%40%3Cdev.commons.apache.org%3E



--
This message was sent by Atlassian Jira
(v8.3.4#803005)