[
https://issues.apache.org/jira/browse/JCR-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732448#comment-15732448
]
Woonsan Ko edited comment on JCR-4077 at 12/8/16 3:10 PM:
----------------------------------------------------------
Hi [[email protected]],
I think the only thing related to http client (indirectly) in
jackrabbit-vfs-ext is the following dependency:
{code}
<!-- For WebDAV client against WebDAV server backend -->
<dependency>
<groupId>org.apache.jackrabbit</groupId>
<artifactId>jackrabbit-webdav</artifactId>
<version>${project.version}</version>
</dependency>
{code}
Actually commons-vfs2 doesn't pull in http or webdav dependencies automatically
either (by using optional).
The reason why jackrabbit-webdav was put there initially was simply because it
was regarded easier to use webdav backend (commons-vfs2 uses jackrabbit-webdav
library optionally when webdav backend is used). However, that was unnecessary.
When people want to use webdav backend with vfs2, they can add all the optional
libraries as well. That's the intention of optional dependencies in
commons-vfs2.
Anyway, I think if we simply remove the jackrabbit-webdav dependency, then it
will work fine. (At least for both local FS and SFTP backend.)
Could you please remove the jackrabbit-webdav dependency locally and see if it
helps?
Thanks in advance,
Woonsan
was (Author: woon_san):
Hi [[email protected]],
I think the only thing related to http client (indirectly) in
jackrabbit-vfs-ext is the following dependency:
{code}
<!-- For WebDAV client against WebDAV server backend -->
<dependency>
<groupId>org.apache.jackrabbit</groupId>
<artifactId>jackrabbit-webdav</artifactId>
<version>${project.version}</version>
</dependency>
{code}
Actually commons-vfs2 doesn't pull in http or webdav dependencies automatically
either (by using optional).
The reason why jackrabbit-webdav was put there initially was simply because it
was regarded easier to use webdav backend because commons-vfs2 webdav url uses
jackrabbit-webdav library. However, that was unnecessary. When people want to
use webdav backend with vfs2, they can add all the optional libraries as well.
That's the intention of optional dependencies in commons-vfs2.
Anyway, I think if we simply remove the jackrabbit-webdav dependency, then it
will work fine. (At least for both local FS and SFTP backend.)
Could you please remove the jackrabbit-webdav dependency locally and see if it
helps?
Thanks in advance,
Woonsan
> disable Jackrabbit VFS Extension (?)
> ------------------------------------
>
> Key: JCR-4077
> URL: https://issues.apache.org/jira/browse/JCR-4077
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-vfs-ext
> Affects Versions: 2.13.6
> Reporter: Julian Reschke
> Fix For: 2.14
>
>
> Switching to the new httpclient code will break jackrabbit-vfs-ext, which has
> a dependency on the older version.
> (Suggestions about how to deal with this welcome)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
