latest-revision is already the default - just this one ivy file is overriding that.
Have you tried, from your project's ivy file, excluding the modules in that one latest-compatible ivy file, and including them as dependencies in your own project file? Maybe a bit cumbersome, but you should be able to fetch them under your conflict manager. On Mon, Jun 23, 2014 at 10:42 AM, Matt Dee <m...@palantir.com> wrote: > Hello, > > I’m not sure if this is the right mailing list, but I have a requirement > and I am trying to determine if it is possible to without changing the Ivy > source code. > > I have a project and I want it to resolve dependencies using the > “latest-revision” strategy. However, one of its dependencies, in its > ivy.xml, specifies > > <conflicts> > <manager name="latest-compatible"/> > </conflicts> > > And so I am getting StrictConflictExceptions. The behavior that I want is > for it to resolve conflicts by always just taking the latest revision. > Setting “latest-revision” to the default conflict manager in the > ivysettings.xml does not work. Is there any way to override the conflict > managers defined in the ivy.xml? > > Thanks! >
