ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Shea <m...@nitido.com>
Subject publishing via http
Date Thu, 01 Apr 2010 21:54:58 GMT
Hi folks,

I am trying to publish to an HTTP Ivy repository, and having some 
trouble with it. I'm using ivy-2.1.0.

The resolver I am using in ivysettings.xml looks like this:

        <url name="shared-publisher">
            <ivy 
pattern="http://${server}/${infrastructure.lib.dir}/${ivy.artifact.pattern}" 
/>
            <artifact 
pattern="http://${server}/${infrastructure.lib.dir}/${ivy.artifact.pattern}" 
/>
        </url>


Basically, I get this in the logs from my ant build when I call ivy:publish:

Caused by: java.io.IOException: Access to URL 
http://[server]/lib/nitido/project24/1.0.0.0/zips/project24-resources.zip 
was refused by the server

If I check the apache logs on the server, I see this:

<snip>
192.168.13.68 - - [01/Apr/2010:17:38:56 -0400] "HEAD 
/lib/nitido/project24/1.0.0.0/zips/project24-resources.zip HTTP/1.1" 401 
224 "-" "Apache Ivy/2.1.0"
192.168.13.68 - testdeveloper1@nitido.com [01/Apr/2010:17:38:56 -0400] 
"HEAD /lib/nitido/project24/1.0.0.0/zips/project24-resources.zip 
HTTP/1.1" 404 163 "-" "Apache Ivy/2.1.0"
192.168.13.68 - - [01/Apr/2010:17:38:56 -0400] "PUT 
/lib/nitido/project24/1.0.0.0/zips/project24-resources.zip HTTP/1.1" 401 
741 "-" "Apache Ivy/2.1.0"
192.168.13.68 - testdeveloper1@nitido.com [01/Apr/2010:17:38:56 -0400] 
"PUT /lib/nitido/project24/1.0.0.0/zips/project24-resources.zip 
HTTP/1.1" 403 538 "-" "Apache Ivy/2.1.0"
</snip>

It looks to me like it's trying to just run a PUT without creating the 
necessary subdirectories first...?

I've also tried messing around with the vfs resolver (compiled my own 
commons-vfs jar, based on the 1.0 tag from the vfs svn repo), but I 
didn't have any luck with it.

I haven't found much about this on google... bits and pieces here and 
there, but nothing that has really helped me yet. Is what I am trying to 
do even possible currently? Or should I just abandon this approach, and 
set up an FTP server to handle publishing instead? =)

Thanks,


Mike Shea.



Mime
View raw message