From steve_l@iseran.com Tue Feb 4 01:00:59 2003
Return-Path:
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 3735 invoked from network); 4 Feb 2003 01:00:59 -0000
Received: from hplb.hpl.hp.com (192.6.10.2)
by daedalus.apache.org with SMTP; 4 Feb 2003 01:00:59 -0000
Received: from snowy.hpl.hp.com (snowy.hpl.hp.com [15.144.94.243])
by hplb.hpl.hp.com (8.12.1/8.12.1/HP Labs Bristol relay) with ESMTP id h1410orP011447
for ; Tue, 4 Feb 2003 01:00:50 GMT
Received: from ranier (ranier.cv.hp.com [15.87.25.18]) by snowy.hpl.hp.com with SMTP (8.7.6/8.7.3 SMKit7.0) id BAA27456 for ; Tue, 4 Feb 2003 01:00:48 GMT
Message-ID: <000e01c2cbe8$e03758d0$1219570f@ranier>
From: "Steve Loughran"
To: "Ant Users List"
References:
Subject: Re: Scaling to large projects
Date: Mon, 3 Feb 2003 17:00:54 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-MailScanner: Found to be clean
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
----- Original Message -----
From: "David McTavish"
To: "'Ant Users List'"
Sent: Monday, February 03, 2003 13:35
Subject: RE: Scaling to large projects
>
> What I was referring in my original email is when you have a project that
> relies on code you have developed in another project. (ie: maven depends
on
> ant). You could either:
> a) have a static binary from project A in the lib folder of project B
I have project B refer to the version in the dist dir of project A, usually.
Unless I want to decouple builds so that B1.12 runs against A1.0 even while
A1.1 is being coded.
> b) dynamically compile and build the library in project A as part of the
> build process of project B.
The trick there is in the toplevel build file
-each sub project has its own targe that calls down to the proejct
-these targets state their dependencies
-so builds from the top do stuff in the right order.
Example:
Then you have targets that call these with the target property set up
right:-