Hello, I put my ivyconf available throught http and keep a local copy when
offline. Work very well for me
<target name="_init-ivy">
<get src="${ivy.conf.url}" dest="${user.home}/.ivy/ivyconf.xml"
ignoreerrors="true" usetimestamp="true"/>
<ivy:configure file="${user.home}/.ivy/ivyconf.xml"
validate="false" />
<ivy:resolve file="${config.dir}/ivy.xml" validate="false"
conf="*" />
</target>
regards
-----Original Message-----
From: Niklas Matthies [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 05, 2007 1:51 PM
To: [email protected]
Subject: Sharing ivyconf.xml
Hello,
In a multi-project enterprise setting, what is the best way to share a
common ivyconf.xml between projects? We're thinking of placing the
ivyconf.xml somewhere in a shared file system, and have each project's
build file reference that location (file path or URL). Does anyone
have experience with this? Is it the usual way to handle things?
It seems (luckily) that there's no need to have versioning of the
ivyconf.xml, in the sense that different versions of a project would
require different versions of ivyconf.xml (which would introduce
dependency issues on ivyconf.xml...). Is that correct, or are there
issues we might be overlooking?
Thanks,
-- Niklas Matthies
