Jing Xue wrote:
On Wed, Sep 26, 2007 at 06:28:41PM +0100, Johan Oskarsson wrote:
The problem with this approach is that you can't have the sftp resolver
be publish only. Instead it tries to use that to read files that it
already tried to read from the url resolver, asking me for the password
every time.
Can you post your ivysettings.xml?
Certainly, here's the latest version:
<ivysettings>
<resolvers>
<chain name="chained">
<url name="ourcompany">
<ivy
pattern="http://ivy.int.ourcompany.com/[organisation]/[module]/[revision]/ivy-[revision].xml"
/>
<artifact
pattern="http://ivy.int.ourcompany.com/[organisation]/[module]/[revision]/[artifact].[ext]"
/>
<artifact
pattern="http://ivy.int.ourcompany.com/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
</url>
<ivyrep name="ivyrep"/>
<sftp user="someuser" host="ivy.int.ourcompany.com">
<ivy
pattern="/var/www/[organisation]/[module]/[revision]/ivy-[revision].xml"/>
<artifact
pattern="/var/www/[organisation]/[module]/[revision]/[artifact].[ext]"/>
</sftp>
</chain>
</resolvers>
<settings defaultResolver="chained"/>
<include url="${ivy.default.conf.dir}/ivyconf-public.xml"/>
<include url="${ivy.default.conf.dir}/ivyconf-shared.xml"/>
<include url="${ivy.default.conf.dir}/ivyconf-local.xml"/>
<include url="${ivy.default.conf.dir}/ivyconf-main-chain.xml"/>
<include url="${ivy.default.conf.dir}/ivyconf-default-chain.xml"/>
</ivysettings>