On Dec 11, 2007 6:58 PM, Niklas Matthies <[EMAIL PROTECTED]> wrote: > On Tue 2007-12-11 at 18:41h, Xavier Hanin wrote on ivy-user: > > On Dec 10, 2007 1:02 PM, Niklas Matthies <[EMAIL PROTECTED]> wrote: > : > > > I wonder whether an EarliestCompatibleConflictManager wouldn't be > > > (even) more useful? It would have the property to yield reproducible > > > results when newer versions are added to the repository. > > > > For build reproducibility we rather recommend to fix revisions when > > publishing your module, > > Ok, I think I'm missing something. Are you suggesting to put a > resolved ivy.xml into source control (along with the regular, > unresolved, evolving ivy.xml) which then should be used to reproduce > builds of the module?
I'm suggesting to use the resolved ivy.xml to reproduce a build. Putting it in source control is a good way to do so, but not the only one. This article is worth reading: http://dead-parrot.de/ivy/ Xavier > > > > but it would be interesting (at least people not > > following this recommendation), so feel free to open an issue. > > Will do so. > > -- Niklas Matthies > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
