Return-Path: 
 <ivy-user-return-3227-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 75063 invoked from network); 5 May 2008 19:12:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 5 May 2008 19:12:24 -0000
Received: (qmail 99036 invoked by uid 500); 5 May 2008 19:12:25 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 99022 invoked by uid 500); 5 May 2008 19:12:25 -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 99011 invoked by uid 99); 5 May 2008 19:12:25 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 May 2008 12:12:25 -0700
X-ASF-Spam-Status: No, hits=0.7 required=10.0
	tests=SPF_SOFTFAIL
X-Spam-Check-By: apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 jimmy@indeed.com does not designate 66.111.4.28 as permitted sender)
Received: from [66.111.4.28] (HELO out4.smtp.messagingengine.com)
 (66.111.4.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 May 2008 19:11:39 +0000
Received: from compute1.internal (compute1.internal [10.202.2.41])
	by out1.messagingengine.com (Postfix) with ESMTP id 22D3B10499B
	for <ivy-user@ant.apache.org>; Mon,  5 May 2008 15:11:51 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
  by compute1.internal (MEProxy); Mon, 05 May 2008 15:11:51 -0400
X-Sasl-enc: JpLSrO39huu5uWNUJN1Yi2ug3YRQE1m6hLRY2+Dob9f4 1210014710
Received: from JIMMY.indeed.com (rrcs-24-153-133-250.sw.biz.rr.com
 [24.153.133.250])
	by www.fastmail.fm (Postfix) with ESMTPSA id 8CF0DAF69
	for <ivy-user@ant.apache.org>; Mon,  5 May 2008 15:11:50 -0400 (EDT)
Date: Mon, 5 May 2008 14:11:43 -0500 (Central Daylight Time)
From: Jimmy Wan <jimmy@indeed.com>
To: ivy-user@ant.apache.org
Subject: Re: transitive dependencies ignoring configuration scope
In-Reply-To: <3bc8237c0805021032m37b7f27dsd675004d255ef6aa@mail.gmail.com>
Message-ID: <alpine.WNT.1.10.0805051409550.3924@WVZZL>
References: <alpine.WNT.1.10.0805011806060.888@WVZZL>
  <3bc8237c0805011803ta64e4a1h59475ad34eb848fe@mail.gmail.com>
  <alpine.WNT.1.10.0805021112540.2592@WVZZL>
  <15412A37E8C9574393B24ADD991FAA7608D5D95DB7@MERCMBX14.na.sas.com>
 <3bc8237c0805021032m37b7f27dsd675004d255ef6aa@mail.gmail.com>
User-Agent: Alpine 1.10 (WNT 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Checked: Checked by ClamAV on apache.org

I had a fundamental misunderstanding of how "*->*" worked.

This fixed my problem, thanks.

On Fri, 2 May 2008, Archie Cobbs wrote:

>You're dependency of Parent to Child does not specify any configuration
>mapping, so you get the default which is "*->*". Probably what you want is:
>
>   <dependencies>
>       <dependency org="MyOrg" name="ChildModule"
>rev="${childmodule.version}" conf="*->master" changing="true"/>
>       <dependency org="junit" name="junit" rev="${junit.version}"
>conf="test->default" />
>   </dependencies>
>
>-Archie
>
>On Fri, May 2, 2008 at 12:12 PM, Jim Adams <Jim.Adams@sas.com> wrote:
>
>> Since test is already defined as test->master, doesn't that make it
>> equivalent to having "master" everywhere?
>>
>> > -----Original Message-----
>> > From: Jimmy Wan [mailto:jimmy@indeed.com]
>> > Sent: Friday, May 02, 2008 12:23 PM
>> > To: ivy-user@ant.apache.org
>> > Subject: Re: transitive dependencies ignoring configuration scope
>> >
>> > My ivy files look like the ones listed below. I tried changing the
>> dependency
>> > in ParentModule on ChildModule to use conf="*->*" but that made no
>> > difference. The ivy reports for master, compile, and default are always
>> > showing TestModule as a dependency of ParentModule because it was a
>> > dependency of common-util in test. It's as though it's ignoring the
>> > "test->default" rule that I stated in childmodule.
>> >
>> > TestModule:
>> > <publications>
>> >     <artifact name="junit" type="jar" ext="jar"/>
>> > </publications>
>> >
>> > ChildModule:
>> >     <configurations>
>> >         <conf name="master"/>
>> >         <conf name="test" extends="master"/>
>> >         <conf name="compile" extends="master"/>
>> >         <conf name="default" extends="master"/>
>> >     </configurations>
>> >
>> >     <publications>
>> >         <artifact name="ChildModule" conf="master"/>
>> >     </publications>
>> >
>> >     <dependencies>
>> >         <dependency org="junit" name="junit" rev="${junit.version}"
>> conf="test->default" />
>> >     </dependencies>
>> >
>> > ParentModule:
>> >     <configurations>
>> >         <conf name="master"/>
>> >         <conf name="test" extends="master"/>
>> >         <conf name="compile" extends="master"/>
>> >         <conf name="default" extends="master"/>
>> >     </configurations>
>> >
>> >     <publications>
>> >         <artifact name="ParentModule" conf="master"/>
>> >     </publications>
>> >
>> >     <dependencies>
>> >         <dependency org="MyOrg" name="ChildModule"
>> rev="${childmodule.version}" changing="true"/>
>> >         <dependency org="junit" name="junit" rev="${junit.version}"
>> conf="test->default" />
>> >     </dependencies>
>> >
>> > On Thu, 1 May 2008, Archie Cobbs wrote:
>> >
>> > >What do the <dependency> sections of each of the three ivy.xml files
>> look
>> > >like?
>> > >
>> > >On Thu, May 1, 2008 at 6:11 PM, Jimmy Wan <jimmy@indeed.com> wrote:
>> > >
>> > >> I'm seeing a problem where dependencies of my dependencies end up in
>> every
>> > >> configuration, but it seems like they shouldn't.
>> > >>
>> > >> Example:
>> > >> TestModule is a dependency of ChildModule for the configuration
>> "test"
>> > >> ChildModule is a dependency of ParentModule with no specified
>> > >> configuration
>> > >> (i.e. all).
>> > >> I now see TestModule as a dependency of ParentModule for all
>> > >> configurations.
>> > >>
>> > >> Am I doing something wrong? TestModule has no stated configurations.
>> > >> ChildModule and ParentModule have the same set of multiple
>> configurations.
>> > >> The "test" configuration and the "default" configuration are both
>> > >> decendants of the "master" configuration.
>> > >>
>> > >> I'm using 2.0.0-beta2.