Ok, so it really seems to be a Commons VFS problem. Could you contact them
to see if they have an idea?
- Xavier
On 4/3/07, Bourzeix, Hervé <[EMAIL PROTECTED]> wrote:
I double check host/usr/pass remote dir, repository exists and it is a
directory. Ivy succeed to resolve artifact from there.
here is an extract of my ivyconf.xml:
<vfs name="remote">
<ivy pattern="
ftp://usr:[EMAIL
PROTECTED]/repository/private/[organisation]/[module]/ivy-[revision].xml"
/>
<artifact pattern="
ftp://usr:[EMAIL
PROTECTED]/repository/private/[organisation]/[module]/[ext]s/[artifact]-[revision].[ext]"
/>
</vfs>
-----Original Message-----
From: Xavier Hanin [mailto:[EMAIL PROTECTED]
Sent: mardi 3 avril 2007 10:35
To: [email protected]
Subject: Re: RE : publish with vfs (ftp)
On 4/3/07, Bourzeix, Hervé <[EMAIL PROTECTED]> wrote:
>
> I did the test and I got the same issue...
> BTW when upgrading the commons-vfs jar, I got the following exception
>
> BUILD FAILED
> java.lang.NoClassDefFoundError:
> org/apache/commons/vfs/provider/webdav/WebdavFileProvider
>
> Removing the jar slide-webdavlib-20050629.161100.jar fix my issue but I
> still get :
>
> BUILD FAILED
> D:\javadev\src\mymod\build-common.xml:267: impossible to publish
artifacts
> for [ genesys | mymod | 1.0 ]:
org.apache.commons.vfs.FileSystemException:
> Could not create folder "ftp://usr:[EMAIL PROTECTED]/repository" because it
> already exists and is a file.
What is strange is that VFS seems to see your 'repository' directory as a
file instead of a directory. Are you sure it isn't the case?
- Xavier
--
Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
--
Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
