Thanks for responding to my question. Now I'm wandering if I need to set the revision= to look for some time of parameter passed to it from the config.xml as the version label (i.e. DEV_10.10) will change and I don't want to hard code it into all dependencies and ivy.xml file for each build. I'm not sure how this will work.
-----Original Message----- From: Adrian Woodhead [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 15, 2008 7:47 AM To: [email protected] Subject: Re: Ivy latest.integration Using "latest.integration" will retrieve whatever Ivy decides is the latest version of an artifact. You can set this to be any specific version you have published if you so desire. For example, if you published version 1.1 of module "x" and then later published version 1.2, using "latest.integration" will retrieve 1.2, but if you set revision="1.1" it will retrieve 1.1 which I think is what you want? [EMAIL PROTECTED] wrote: > Can anyone help me out with my question below? Thanks in advance. > > -Michael > > _____________________________________________ > From: Smith Michael (FVY9DST) > Sent: Tuesday, October 14, 2008 11:43 AM > To: [email protected] > Subject: Ivy latest.integration > > Hello, > > I'm new to Ivy Publisher and it's currently used with Cruise Control v2.5. > The scripts are working fine and the source control tool is PVCS Version > Manager 8.1.3. > > All builds are fine as long as we are monitoring the tip versions. But this > is now getting out of control and we need to apply a version label to the > artifacts and build based on that. I noticed in the scripts the revision is > set to: rev="latest.integration". Is there a way we can set it to: > rev="DEV-10.10" or any assigned version label? > > We have about 48-50 components and there are inter-dependencies with several. > I want to institute branching as well, thus also introduces floating the > label when check-in's take place and we could be on 2-3 different build > labels at the same time. > > Any help would be greatly appreciated. > > > >
