ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gareth Western <>
Subject Re: Multi-module dependency configuration
Date Fri, 10 Jul 2009 18:37:22 GMT
Hmmm, so it appears that when module A (the webapp) declares module B
(jar) as a dependency then then j2ee.jar (B's dependency) is not
included. However when I also declare module C (another jar, which is
also dependent on both module B and the j2ee.jar) as a dependency of A
then the j2ee.jar starts to get included in A (presumably as a
transitive depdency, somehow?). But I still don't understand why,
because A declares both B and C dependencies with
conf="war->jar;compile->compile" and the j2ee.jar is always listed in
every ivy.xml with conf="compile->default", which I thought would mean
it shouldn't be included when using the "war" configuration?

Sorry if i'm not making much sense. I've been looking at this for too long!



On Fri, Jul 10, 2009 at 7:23 PM, Gareth Western<> wrote:
> So now the webapp compiles, however the "compile-time-only" jar is
> still being brought into the webapp's WEB-INF/lib folder somehow. If I
> use Ivy to generate a dependency report, it says that the jar is
> required by 3 of the other modules, however in the ivy file for each
> of those modules the j2ee.jar is specified with
> conf="compile->default":
>    <dependency org="j2ee" name="j2ee" rev="1.3.1" conf="compile->default"/>
> so I don't see how it could be being involved in the "war"
> configuration from the webapp module.
> I'm not sure how to explain the whole scenario without attaching all
> the files involved (there are 5 modules in total, each with a
> build.xml and ivy.xml). Does anyone have any tips for how to track
> down exactly what's happening?

View raw message