Return-Path: 
 <ant-user-return-24438-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 91690 invoked from network); 30 Aug 2002 22:26:53 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 30 Aug 2002 22:26:53 -0000
Received: (qmail 24428 invoked by uid 97); 30 Aug 2002 22:27:21 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 24412 invoked by uid 97); 30 Aug 2002 22:27:20 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Id: "Ant Users List" <ant-user.jakarta.apache.org>
Reply-To: "Ant Users List" <ant-user@jakarta.apache.org>
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 24400 invoked by uid 98); 30 Aug 2002 22:27:20 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
Message-ID: 
 <88925B2D74CCD311A2AB009027DC661301916DFB@mail.carnegielearning.com>
From: "McHenry, Matt" <mmchenry@carnegielearning.com>
To: "Ant-User (E-mail)" <ant-user@jakarta.apache.org>
Cc: 'Matt Lyon' <matt@stargus.com>
Subject: RE: Automated source config model?
Date: Fri, 30 Aug 2002 18:26:46 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25074.5396BCB2"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

------_=_NextPart_001_01C25074.5396BCB2
Content-Type: text/plain;
	charset="windows-1252"

> I'm curious as to how others have faced this challenge using 
> Ant and CVS in a production build environment. One thought I 
> had was to investigate using the Ant-Contrib <foreach> task 
> to iterate over a 'src.properties' file that would contain 
> the ingredients, so to speak, that are passed to a fetch 
> target (e.g a <cvs> task that would read in the 
> 'src.properties' file and grab the correct revisions of every 
> file needed to build the product for a specific developers' 
> build case).

	I have a setup that does basically what you're talking about
(although we just use it for automated builds -- our stuff isn't complex
enough that developers have a need for this kind of automation).  IMO,
you're on exactly the right track with the foreach task.  Each cvs tag has
an associated list of directories (or individual files).  The property file
contains a list of these (tag,directory-list) pairs.  It's then very
straightforward to iterate over each of the directories associated with each
of the tags and do the appropriate cvs checkout command.

	I hadn't thought that my setup was all that interesting (and it
certainly isn't all that complex), but if folks are interested I can inquire
about getting permission to make it available.


Matt McHenry
Software Developer
Carnegie Learning, Inc.

------_=_NextPart_001_01C25074.5396BCB2--