latest strategies and build reproducability

["Loehr, Ruel" <rl...@pointserve.com>]

Maybe a dumb question.

I'm not taking advantage of using the latest strategies and am investigating it.

If proj b depends on proj a   and b defines a dependency on a that is "latest.integration".....

I do an "official" release of proj b which tags it in svn.    At that time the ivy.xml is tagged with the "latest.integration" value which is bad of course for reproducibility purposes.

How are you guys handling this in real world situations?

I assume you just change that value prior to releasing and maybe have a build task which ensures there are no dynamic rev's at release time?

R

Re: latest strategies and build reproducability

[Niklas Matthies <ml...@nmhq.net>]

On Thu 2008-06-19 at 10:37h, Loehr, Ruel wrote on ivy-user:
:
> I do an "official" release of proj b which tags it in svn.    At
> that time the ivy.xml is tagged with the "latest.integration" value
> which is bad of course for reproducibility purposes.
:
> I assume you just change that value prior to releasing and maybe
> have a build task which ensures there are no dynamic rev's at
> release time?

This page describes an alternative approach: http://dead-parrot.de/ivy/

-- Niklas Matthies