Yeah, I was trying to avoid something like that, but it seems the best route to take now.
I just tried the multi setting strategy, but that doesn't work due to the ivy cache already have the new integration builds. Maybe it'd be good in ivy to be able to match on the organization or other properties, and then massage the version as needed before resolving. -----Original Message----- From: Niklas Matthies [mailto:[email protected]] Sent: Wednesday, August 26, 2009 10:26 AM To: [email protected] Subject: Re: set latest strategy with a property You could use XSLT in your builds to replace any dependency revisions in the ivy.xml by lastest.<whatever>. Or, if you always use latest.<something> as your version dependencies, you could have <dependency ... rev="latest.${build.type}"> for all dependencies and set the build.type property appropriately in your build scripts. -- Niklas Matthies On Wed 2009-08-26 at 10:01h, Jonathan Roberts wrote on ivy-user: > > So after doing some research, I guess I'm going to setup different ivy > settings for the different types of builds. Instead of relying on > different statuses, the ivy.xml files will pretty much always use > latest.integration for internal dependencies, but will restricted by the > resolvers/repositories. > > Integration builds will be able to see integration, nightly and release > resolvers. > Nightly builds will be able to see nightly and release > And release builds will only be able to see release builds. > > Anyone have an easier/better way of doing this? > > Thanks > Jon > > > -----Original Message----- > From: Jonathan Roberts [mailto:[email protected]] > Sent: Tuesday, August 25, 2009 4:27 PM > To: [email protected] > Subject: set latest strategy with a property > > > Hello again, > > We do 3 types of builds, nightly, integrations, and releases. > > Is there a way to set the latest strategy using an ant property? I want > to make sure that my nightly builds only use latest.nightly and releases > only use latest.release. Then for regualar dev builds just use > latest.integration. It'd be good to be able to do this without > constantly having to change the individual ivy.xml files. > > Can I do this with modules? > > Jon Roberts
