[
https://issues.apache.org/jira/browse/VFS-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954459#comment-16954459
]
Woonsan Ko commented on VFS-686:
--------------------------------
It seems working fine after building/running from master branch.
I've followed [1] to test run webdav3 and webdav4 providers after running
Jackrabbit Standalone server [2], which provides WebDAV server as well, locally.
Thank you very much!
Woonsan
[1]
https://github.com/apache/commons-vfs/blob/master/commons-vfs2-examples/README.md#example-test-scenario-with-webdav3
[2] http://jackrabbit.apache.org/jcr/standalone-server.html
> Upgrade Jackrabbit dependency to the latest 2.x
> -----------------------------------------------
>
> Key: VFS-686
> URL: https://issues.apache.org/jira/browse/VFS-686
> Project: Commons VFS
> Issue Type: Improvement
> Affects Versions: 2.2
> Reporter: Woonsan Ko
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.5.0
>
> Attachments: feature-VFS-686-2.patch, feature-VFS-686-3.patch,
> feature-VFS-686-4.patch, feature-VFS-686-5.patch, feature-VFS-686-6.patch,
> feature-VFS-686.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The current dependency, Jackrabbit 1.6.5, still depends on HttpClient 3.x,
> while Jackrabbit 2.x depends on HttpClient 4.x.
> So, WebDAV file system provider should use the latest stable version of
> Jackrabbit 2.x.
> As of VFS-360, it is possible to let the WebDAV file system use
> HttpComponents 4.x.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
