[ 
https://issues.apache.org/jira/browse/IVY-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594905#action_12594905
 ] 

David Seymore commented on IVY-643:
-----------------------------------

So, i'm not ready to jump to ivy 2 
(http://www.audioscrobbler.net/development/ivysvn/ requires); and the older 
project ivy+svn is just.. way out of the loop and didn't support PUT 
operations. So, I wrote a 1.4.1 compatible ivy svn resolver. 

http://code.google.com/p/ivymeetsvn

Its a work in progress. but, took very little time to get up and running.... 
versus spending days trying to get ivy+svn up to speed.  I've given up on just 
webdav.. I like the idea of having versioning on the repository. 

> 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.

Reply via email to