You should be able to control this by using <mapping> elements nested
into <makepom>.
Matt
On Tue, Oct 16, 2012 at 4:15 PM, Not Zippy <notzi...@gmail.com> wrote:
> Hi
>
> For some reason I hadn't noticed till now that when I used ant + ivy to
> build my POMS that it created all the dependencies as "optional"
> ie
> <dependency>
> <groupId>commons-io</groupId>
> <artifactId>commons-io</artifactId>
> <version>2.2</version>
> <optional>true</optional>
> </dependency>
>
> My ivy.xml looks like
> <ivy-module version="1.0">
> <info
> organisation="xxx"
> module="ext-dx"
> status="integration"/>
> <configurations defaultconf="main">
> <conf name="core" visibility="private" />
> <conf name="common" extends="core" />
> <conf name="main" extends="core" />
> <conf name="default" extends="main" />
> <conf name="resource" extends="core" />
> <conf name="hidden" extends="core" />
> <conf name="test" extends="common" />
> </configurations>
> <publications>
> <artifact name="ext-dx" type="jar" conf="main"/>
> <artifact name="ext-dx" type="pom" conf="main"/>
> <artifact name="ext-dx-resource" type="zip" ext="zip" conf="main"/>
> <artifact name="ext-dx-sources" type="source" ext="jar" conf="main"/>
> </publications>
> <dependencies>
> <dependency conf="main->default" org="commons-io" name="commons-io"
> rev="2.2"/>
> ....
>
> Make pom is
> <ivy:makepom ivyfile="${basedir}/ivy.xml"
> conf="default"
> pomfile="${build.dir}/${artifact.name}.pom">
> <mapping conf="default" scope="compile"/>
> <mapping conf="default" scope="runtime"/>
> </ivy:makepom>
>
> Anyone have idea why ? Can't see anything about it in the docs...
>
> THANKS
> nZ
