Solve conflicts in ivy dependencies

It seems that updating the commons codec version is creating conflicts in some metrics projects where some dependencies are being "evicted" (this is happening in DescriptorParser:

[ivy:resolve] :: resolution report :: resolve 49307ms :: artifacts dl 20132ms
[ivy:resolve] 	:: evicted modules:
[ivy:resolve] 	org.mockito#mockito-core;1.9.5 by [org.mockito#mockito-core;1.10.19] in [default]
[ivy:resolve] 	junit#junit;4.10 by [junit#junit;4.12] in [default]
[ivy:resolve] 	xml-apis#xml-apis;1.0.b2 by [xml-apis#xml-apis;1.3.04] in [default]
[ivy:resolve] 	junit#junit;3.8.1 by [junit#junit;4.13] in [default]
[ivy:resolve] 	junit#junit;4.12 by [junit#junit;4.13] in [default]
[ivy:resolve] 	com.fasterxml.jackson.core#jackson-annotations;2.8.0 by [com.fasterxml.jackson.core#jackson-annotations;2.8.6] in [default]
[ivy:resolve] 	com.google.guava#guava;18.0 by [com.google.guava#guava;19.0] in [default]
[ivy:resolve] 	javax.servlet#servlet-api;2.3 by [javax.servlet#servlet-api;2.5] in [default]
[ivy:resolve] 	org.powermock#powermock-module-junit4;1.6.4 by [org.powermock#powermock-module-junit4;1.6.5] in [default]
[ivy:resolve] 	org.powermock#powermock-api-mockito;1.6.4 by [org.powermock#powermock-api-mockito;1.6.5] in [default]
[ivy:resolve] 	org.apache.commons#commons-lang3;3.5 by [org.apache.commons#commons-lang3;3.8] in [default]
[ivy:resolve] 	junit#junit;4.11 by [junit#junit;4.13] in [default]
[ivy:resolve] 	commons-logging#commons-logging;1.1.1 by [commons-logging#commons-logging;1.1.3] in [default]
[ivy:resolve] 	commons-codec#commons-codec;1.6 by [commons-codec#commons-codec;1.15] in [default]
[ivy:resolve] 	org.slf4j#slf4j-api;1.7.2 by [org.slf4j#slf4j-api;1.7.19] in [default]
[ivy:resolve] 	org.slf4j#slf4j-api;1.7.19 by [org.slf4j#slf4j-api;1.7.22] in [default]
[ivy:resolve] 	junit#junit;4.8.1 by [junit#junit;4.13] in [default]
[ivy:resolve] 	org.objenesis#objenesis;1.2 by [org.objenesis#objenesis;2.2] in [default]
[ivy:resolve] 	org.slf4j#slf4j-api;1.6.6 by [org.slf4j#slf4j-api;1.7.22] in [default]

It seems that Ivy has a conflict manager that should take care of not evitting modules: https://ant.apache.org/ivy/history/2.0.0/settings/conflict-managers.html

This is invoked by adding a line at the end of the dependencies section.