You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Antoine Levy-Lambert (JIRA)" <ji...@apache.org> on 2010/05/25 23:55:33 UTC

[jira] Commented: (IVY-1193) Trying to move Ivy to an HTTP-based publish model, we discovered that it doesn't perform a MKCOL before doing a PUT.

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

Antoine Levy-Lambert commented on IVY-1193:
-------------------------------------------

Hi,

using WebDAV is possible using the vfs resolver.

In my project we are using the vfs resolver and a vfs provider that we wrote ourselves based on jackrabbit.

My colleague who wrote the vfs provider tells me that vfs ships with another webdav provider now. This was not the case when we did our development obviously.

You should try the vfs solution. If you have issues, write it in this ticket.

The url resolver is not doing MKCOL operations, maybe it is thought for servers which do not implement the full WebDAV spec but which have upload servlets.

Regards,

Antoine

> Trying to move Ivy to an HTTP-based publish model, we discovered that it doesn't perform a MKCOL before doing a PUT.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-1193
>                 URL: https://issues.apache.org/jira/browse/IVY-1193
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0
>         Environment: All environments.
>            Reporter: Ervin Beba
>
> The problem is that when Ivy attempts to publish to a URL resolver via HTTP, it does not adhere to the WebDav requirement that you create the parent path (parent collections) with a MKCOL command before the PUT command. Ivy incorrectly just attempts to PUT artifacts to a path which hasn't been created.

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