Return-Path: 
 <ivy-user-return-5546-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 23990 invoked from network); 10 Jul 2009 18:37:44 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 10 Jul 2009 18:37:44 -0000
Received: (qmail 78757 invoked by uid 500); 10 Jul 2009 18:37:54 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 78703 invoked by uid 500); 10 Jul 2009 18:37:53 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 78693 invoked by uid 99); 10 Jul 2009 18:37:53 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jul 2009 18:37:53 +0000
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [74.125.78.148] (HELO ey-out-1920.google.com) (74.125.78.148)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jul 2009 18:37:45 +0000
Received: by ey-out-1920.google.com with SMTP id 5so243990eyb.0
        for <ivy-user@ant.apache.org>; Fri, 10 Jul 2009 11:37:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.52.194 with SMTP id e44mr652331wec.34.1247251042478; Fri,
	10 Jul 2009 11:37:22 -0700 (PDT)
In-Reply-To: <34458dc50907101123i1a1d71a0g8fd34aeb4195389e@mail.gmail.com>
References: <34458dc50907100654h661e5756m8b341f70b3daafa7@mail.gmail.com>
	 <COL118-W65A4381EF0EDE865E9B182AD270@phx.gbl>
	 <34458dc50907101123i1a1d71a0g8fd34aeb4195389e@mail.gmail.com>
Date: Fri, 10 Jul 2009 19:37:22 +0100
Message-ID: <34458dc50907101137u783019a4m29807f4c64e59b92@mail.gmail.com>
Subject: Re: Multi-module dependency configuration
From: Gareth Western <gareth@garethwestern.com>
To: ivy-user@ant.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

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=3D"war->jar;compile->compile" and the j2ee.jar is always listed in
every ivy.xml with conf=3D"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!

Cheers,

Gareth

On Fri, Jul 10, 2009 at 7:23 PM, Gareth Western<gareth@garethwestern.com> w=
rote:
>
> 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=3D"compile->default":
> =A0 =A0<dependency org=3D"j2ee" name=3D"j2ee" rev=3D"1.3.1" conf=3D"compi=
le->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?
>