You may not need/want the visibility to be private, I just tend to do that when I have a configuration whose purpose is support and is not really meant to be used outside of the current module.
On Tue, Jul 21, 2009 at 8:51 PM, Joshua Tharp < [email protected]> wrote: > Might you achieve the same thing with three configurations instead? > > <conf name="base" visibility="private" /> > <conf name="runtime" extends="base" /> > <conf name="web" extends="base" /> > > > On Tue, Jul 21, 2009 at 8:20 PM, Chris Nokes <[email protected]> wrote: > >> Here's the confs for a module I depend on: >> runtime >> web extends runtime >> >> "runtime" represents the jars to be added to the EAR. >> "web" represents the compile classpath for the module. Web must extend >> runtime because I want the jar set of runtime and web to be binary >> compatible and resolve conflicts. >> >> I would like to do the following in my target module: >> webPackaging->web,!runtime >> >> >> "webPackaging" represents the jars to be added to the WAR. !runtime means >> do not add any jars from the runtime conf. >> >> Is there a way to do this with Ivy? >> >> Thanks, >> Chris Nokes >> >> >> >> >
