ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Woodhead <adr...@last.fm>
Subject Re: vfs dav/http resolver
Date Thu, 14 May 2009 17:59:04 GMT
Kaygee, I'm not sure about the others, but I can't access those URL's, I 
get:

The connection was refused when attempting to contact 192.168.0.104.

I'm assuming those are internal IP addresses which aren't accessible by 
the rest of the world...

kaygee wrote:
> Sorry to reply to myself... but after reading some other posts I see that the
> ibilio resolver may also work for my purposes. However it appears that the
> ibilio resolver pattern accesses the repository in a different way than the
> svn publisher even though they appear the same to me.
>
> The SVN install creates the following.
>
> http://192.168.0.104/svn/ivy/internal/com.kaygee/Fake-DataGraph/5/
>
> but the ibilio resolver attempts the following.
>
> http://192.168.0.104/svn/ivy/internal/com/kaygee/Fake-DataGraph/5/
>
> I believe that the com.kaygee is coming from the ivy.xml info tag which is
> as follows.
>
> <info organisation="com.kaygee" module="depends"/>
>
> Here's my resolvers...
>
> <svn name="ivysvn" userName="${svn.user.name}"
> userPassword="${svn.user.password}"
> repositoryRoot="http://192.168.0.104/svn" >
> <ivy pattern="ivy/internal/[organisation]/[module]/[revision]/ivy.xml" />
> <artifact
> pattern="ivy/internal/[organisation]/[module]/[revision]/[artifact].[ext]"
> />
> </svn>
>
> <ibiblio name="svn.repo" m2compatible="true" usepoms="false"
> root="${svn.repo}"
> pattern="ivy/internal/[organisation]/[module]/[revision]/[artifact].[ext]">
> </ibiblio>
>
> I apologize for my ineptitude. :)
>
> kg
>
>
> kaygee wrote:
>   
>> I'm using the svn resolver to install libraries and dav to advertise them,
>> but I'd like to try the vfs resolver in projects to retrieve the libraries
>> so I don't require people add the ivysvn libs to their Ant library. I've
>> noticed that in the ivy.jar I have (2.1.0-rc1) the http provider is
>> commented out... is the vfs http resolver available?
>>
>>     <!--
>>     <provider
>> class-name="org.apache.commons.vfs.provider.http.HttpFileProvider">
>>         <scheme name="http"/>
>>         <if-available
>> class-name="org.apache.commons.httpclient.HttpClient"/>
>>     </provider>
>>     -->
>>
>>
>>     
>
>   

Mime
View raw message