Xavier,
Thanks for the quick turnaround on this.
I've tried it, and as you said, it works (even if it's not documented).
Here are the settings (so far) in the remote directory:
<ivysettings>
<property name="repo.path" value="/home/ivyrep/repo" />
<resolvers>
<url name="local-http" >
<ivy
pattern="${ivy.settings.dir}/[organization]/[module]-ivy-[revision].xml" />
<artifact
pattern="${ivy.settings.dir}/[organization]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
<artifact
pattern="${ivy.settings.dir}/[organization]/[module]/[revision]/[artifact].[ext]"
/>
</url>
<sftp name="local-sftp" host="${ivyrepo.host}"
port="${ivyrepo.port}" user="${ivyrepo.user}"
userPassword="${ivyrepo.password}" >
<ivy
pattern="${repo.path}/[organization]/[module]-ivy-[revision].xml" />
<artifact
pattern="${repo.path}/[organization]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
<artifact
pattern="${repo.path}/[organization]/[module]/[revision]/[artifact].[ext]"
/>
</sftp>
</resolvers>
</ivysettings>
I've been able to retrieve with both resolvers. I'm sure that I'll have
to add more options once we get going for real. I expect we'll need to
have integration (SNAPSHOT) builds, and separate configurations for
building and testing, so I'm sure this will evolve before we're fully
running.
(I've also tried specifying
the settings file url in the <settings> or <configure> node, and that
doesn't work properly: it still looks for ivysettings.xml in my local
directory)
This is strange and is clearly a bug. Could you open an issue with more
details about what you tried?
All I tried was specifying an HTTP url in the <settings> tag. Thinking
about it now, it's not something that really would have helped: we're
going to need some local configuration options, and this approach would
not have worked.
Dave
