I\'m using Ivy for project dependency management and it\'s been working well aside from one issue which I\'ve always had. There are certain dependencies that Ivy is downloa
Try setting the left side of conf mapping to default. For example conf="runtime->default"
That resolved my issue.
Edit: This can be found in ivy.xml, in the <dependency>
tag. For eg:
<dependencies>
<dependency conf="runtime->default" name="jsf-api" org="com.sun.faces" rev="2.2.13"/>
</dependencies>
The part ->default
is the key.
Found the issue. The problem was that the missing dependencies were "bundle" and my ant script was set to only install "jar" ...
<ivy:retrieve pattern="${ivy.lib.dir}/[artifact].[revision].[ext]"
type="jar"
sync="true" />
Fixed version:
<ivy:retrieve pattern="${ivy.lib.dir}/[artifact].[revision].[ext]"
type="jar,bundle"
sync="true" />
You should verify the conf
mapping you're using for those missing jars. In particular, if you have a conf
of, say, compile
for log4j it won't actually retrieve anything because log4j is published with a conf
of maste
r. You'd need to set your conf
to something like compile->master
. You then need to repeat with the other artifacts that are missing.