On Mon 2007-12-10 at 10:41h, Jing Xue wrote on ivy-user: : > If I understand it correctly, isn't this resolution process only > involved when the module is having its dependencies resolved for the > first time, prior to publish? Once it's published, the dependencies > are fixed in the published version of ivy.xml, which is anchored by a > versioned repository. So when this module A participates in the > resolution process of another module B, the original ivy settings > under which A was resolved shouldn't matter at all.
The ivy settings might define a latest-strategy for module A (or dependencies of module A) for example if it uses a non-standard version numbering scheme. That's just one example how Ivy settings are still relevant to "fixed" published dependencie. > ...right? (argh this thing makes my head hurt. :-) ) Mine too. ;) -- Niklas Matthies
