Do you mean backported? Very little chance, this conflict manager was pretty difficult to implement and required some changes in dependency resolution logic which has already been updated in 2.0 stream. But you have all the commit logs on the issue to see how it has been implemented, so feel free to backport the changes :-)
Xavier > -----Original Message----- > From: Crystal, Mayer [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 06, 2007 10:53 AM > To: ivy-user@incubator.apache.org > Subject: RE: Question about revision conflicts during resolve/retrieve > > This wouldn't by chance be backward compatible with 1.4, would it? :) > > -----Original Message----- > From: Xavier Hanin [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 06, 2007 10:51 AM > To: ivy-user@incubator.apache.org > Subject: RE: Question about revision conflicts during resolve/retrieve > > > -----Original Message----- > > From: Crystal, Mayer [mailto:[EMAIL PROTECTED] > > Sent: Thursday, December 06, 2007 10:47 AM > > To: ivy-user@incubator.apache.org > > Cc: Etkine, Dmitri > > Subject: Question about revision conflicts during resolve/retrieve > > > > We are using Ivy 1.4.1 and had a question about conflict resolution > > between 2 modules. Let's say we have a setup like: > > > > A depends on B version 1.4 and C version 1.5 B depends on C version > > 1.+ Version C in the repository is 1.7 > > > > > > Is there a way to tell ivy that when it is resolving, if it comes > > across a firm requirement (1.5 for C for module A) which doesn't > > conflict with other requirements (the 1.+ for C for module B) to > > always choose the strict requirement? > This is exactly what the latest-compatible-conflict-manager introduced > recently do: > https://issues.apache.org/jira/browse/IVY-648 > > This is available in trunk and will be too in 2.0.0 beta 1 which is > just > around the corner. > > Xavier > > > > > > > > > Thanks, > > Mayer
