I think ivy-local should require maven-local otherwise the xmvn resolver in /etc/ivy/ivysettings.xml is non-functional. Without maven-local: [ivy:resolve] [ivy:resolve] :: problems summary :: [ivy:resolve] :::: WARNINGS [ivy:resolve] [XMvn] No XMvn configuration files were found. Using default embedded configuration. [ivy:resolve] module not found: xmlenc#xmlenc;0.52 [ivy:resolve] ==== local: tried [ivy:resolve] /root/.ivy2/local/xmlenc/xmlenc/0.52/ivys/ivy.xml [ivy:resolve] -- artifact xmlenc#xmlenc;0.52!xmlenc.jar: [ivy:resolve] /root/.ivy2/local/xmlenc/xmlenc/0.52/jars/xmlenc.jar [ivy:resolve] module not found: commons-codec#commons-codec;1.4 .... With maven-local: ivy-resolve: [ivy:resolve] :: resolving dependencies :: org.apache.pig#pig;0.12.0 [ivy:resolve] confs: [master, default, runtime, compile, test, javadoc, releaseaudit, jdiff, checkstyle, buildJar, hadoop20, hadoop23, hbase94, hbase95] [ivy:resolve] found xmlenc#xmlenc;SYSTEM in xmvn [ivy:resolve] [SYSTEM] xmlenc#xmlenc;0.52 (forced) [ivy:resolve] found commons-codec#commons-codec;SYSTEM in xmvn [ivy:resolve] [SYSTEM] commons-codec#commons-codec;1.4 (forced) ....
This will be fixed in new major upstream release. As a workaround you can add explicit requires on maven-local. *** This bug has been marked as a duplicate of bug 1057174 ***