Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gerard.fernandes@lehman.com
 designates 192.147.56.151 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Cache Path and Ant console logging
Date: Thu, 4 Oct 2007 16:48:50 +0100
Message-ID: 
 <F8B862EC45662D41AE74534FE40BE1C1049741C8@lopets1exms002.leh.lbcorp.lehman.com>
In-Reply-To: <4704F74F.6060307@apache.org>
Thread-Topic: Cache Path and Ant console logging
Thread-Index: AcgGkk0CJ0rXqDGeRgaEpC3vMgiZmAACOclg
References: 
 <F8B862EC45662D41AE74534FE40BE1C1049741B2@lopets1exms002.leh.lbcorp.lehman.com>
 <F8B862EC45662D41AE74534FE40BE1C1049741B3@lopets1exms002.leh.lbcorp.lehman.com>
 <4704F74F.6060307@apache.org>
From: "Fernandes, Gerard" <gerard.fernandes@lehman.com>
To: <ivy-user@incubator.apache.org>
X-messagegate_id: D3913A2B9C5
X-Virus-Checked: Checked by ClamAV on apache.org


Thanks for the post Steve. I can see how this would be good, although I
personally would prefer to break out a common build system that supplied
(via Ivy) a global repository with artefacts and then use Ivy again to
manage dependencies in modules that needed them. That way, the build
system need only be concerned with building it's own artefact(s).

A packaging system could then manage, again via Ivy, the packaging of a
deployable unit along with all it's dependencies.

But of course, that's a different issue. :)

Could you point me to such global datatypes in Ant that can be
inherited?

Thanks again.

Gerard.

-----Original Message-----
From: Steve Loughran =5Bmailto:stevel=40apache.org=5D=20
Sent: 04 October 2007 15:23
To: ivy-user=40incubator.apache.org
Subject: Re: Cache Path and Ant console logging

Fernandes, Gerard wrote:
>=20
> Ok, I've tried to debug this a bit and it seems the problem is not Ivy

> - it's the way Ant handles global declarations when calling out to=20
> external build scripts. This causes the global cache-path tasks to be=20
> re-invoked each time a call to an externally defined target happens,=20
> therefore triggering repeated resolutions.
>=20
> This is not an Ivy issue. It is an Ant build script structure issue.


yes, if you use <antcall> or <subant> then things get triggered
repeatedly.  This can be a good thing if you want sub projects to have
different dependencies. To pass state down , get the data into ant
datatypes that can be inherited.

--=20
Steve Loughran                  http://www.1060.org/blogxter/publish/5
Author: Ant in Action           http://antbook.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - =
- - - - - - -

This message is intended only for the personal and confidential use of the =
designated recipient(s) named above.  If you are not the intended =
recipient of this message you are hereby notified that any review, =
dissemination, distribution or copying of this message is strictly =
prohibited.  This communication is for information purposes only and =
should not be regarded as an offer to sell or as a solicitation of an =
offer to buy any financial product, an official confirmation of any =
transaction, or as an official statement of Lehman Brothers.  Email =
transmission cannot be guaranteed to be secure or error-free.  Therefore, =
we do not represent that this information is complete or accurate and it =
should not be relied upon as such.  All information is subject to change =
without notice.