Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <1592776634.1207759405190.JavaMail.jira@brutus>
Date: Wed, 9 Apr 2008 09:43:25 -0700 (PDT)
From: "Ivan \"Rambius\" Ivanov (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Updated: (IVY-643) Ship ivy with commons-vfs-sandbox.jar,
 because it provides the webdav support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ivan "Rambius" Ivanov updated IVY-643:
--------------------------------------


David, the Subversion server or more specifically mod_dav_svn implements a superset of the WebDAV specification and it is called Delta V and is available as an RFC draft. Delta V deals mainly with versioning as this topic was exlcuded from the original WebDAV protocol because of its complexity. There are fully complaint Delta V servers and clients and Subversion does not fully comply as well.

Anyway, Subversion support all WebDAV requests plus some of the Delta V ones. You can technically send a dav PUT request to a Subverion/mod_dav_svn, but it will reject it. The reason is that Delta V says that before you PUT a file, you have to do a CHECKOUT request on it. This is roughly how it works.

Anyway, Subversion can be configured to work as a WebDAV server, thus accepting generic WebDAV requests. The configuration is described in Appendix C "WebDAV and Autoversioning" [1], section "Autoversioning", [2] in the Subversion book. Use the directive

SVNAutoversioning on

in your httpd.conf to turn autoversioning on. Now, if you send for example a PUT request for a file, it will do all the Delta V hassle to CHECKOUT the file, PUT  it and CHECKIN. Subversion also assign auto-generated comments to such files.

Thus an ordinary webdav client can use the SVN repository.

[1] http://svnbook.red-bean.com/en/1.4/svn.webdav.html
[2] http://svnbook.red-bean.com/en/1.4/svn.webdav.autoversioning.html

> Ship ivy with commons-vfs-sandbox.jar, because it provides the webdav support
> -----------------------------------------------------------------------------
>
>                 Key: IVY-643
>                 URL: https://issues.apache.org/jira/browse/IVY-643
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0.0-alpha-2
>            Reporter: Ivan "Rambius" Ivanov
>
> The commons-vsf project has been split into commons-vfs.jar and commons-vfs-sandbox.jar. The webdav support is provided by commons-vfs-sandbox.jar, see http://commons.apache.org/vfs/index.html : "Due to some technical reasons we had to move the webdav and jcifs (smb) filesystem to the sandbox. So if you need one of these filesystems you have to build VFS manually."
> Ivy does not come with commons-vfs-sandbox.jar and I believe it should in order to prevent its users from the hassle of building commons-vfs themselves. I myself built it from commons-vfs 1.0 source.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.