Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 43951 invoked from network); 9 Aug 2002 23:24:59 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 9 Aug 2002 23:24:59 -0000 Received: (qmail 8367 invoked by uid 97); 9 Aug 2002 23:25:20 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 8350 invoked by uid 97); 9 Aug 2002 23:25:20 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 8338 invoked by uid 98); 9 Aug 2002 23:25:19 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: From: suu_quan@non.agilent.com To: ant-user@jakarta.apache.org Subject: Help with designing Tibco Interface builds Date: Fri, 9 Aug 2002 17:24:53 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Put on the spot right today, It's august 9th, and I got to have everything tested and ready by the 22nd, and I've decided to use Ant as my main release tool, and I'm a real novice at this Ant stuff, no wonder I'm panicking right now. To top that, I'm the only knowledgeable Ant person in the team. Tough job when it's done and I try to explain it to them. This Tibco project has 25 independent interfaces (or components used interchangeably here), plus 1 common/shared component. I should be able to say: build interface1 intf5 and intf15 for example The directory structure is like this root/ /shared /interface1 ... /interface25 The shared component has its own rule, and there is nothing out of the ordinary. The 25 component builds use the same rules. The only difference is the top directory for the interface and probably some other properties (they said none, but I know better: they'll be coming later). Question 1: How would I design my build.xml? I do not see how I can parametrize a task like a function call and pass it the top directory of the interface and maybe lateron other properties (I'm still very much scripting in my mind). Or do I copy the same build.xml to each interface and call it from the top level interface? The build has some C++ and Java build part: that part, I feel a little more confident. It's what comes below that bothers me. Each directory has a MATRIX of where to deliver the files. For example: development:.../config/aaaa should go to machine1:/xxx/aaaa development:.../custom/bbbb should go to machine1:/yyy/bbbb and machine3:/zzz/bbbb and lots of that kind of combination. How would you handle that? I'm tempted to do it in Perl, since I'm already familiar with it. We use Clearcase, and there is a step to checkout certain files, fill in some info, check it back in. I know there is a clearcase task. What do I gain in using the clearcase task over writing a perl script myself? Mea culpa, nobody forces me to use Ant (1.5), now I need to be saved. tia Suu Quan Configuration Management & Release Engineering Agilent Technologies Bldg 53, Post F4 (408)553-4338 (untill further notice) Bldg 54, Post P4 (408)553-7155 (don't use) cell (408)420-6687 5301 Stevens Creek Blvd Santa Clara, CA 95051 suu_quan@non.agilent.com -- To unsubscribe, e-mail: For additional commands, e-mail: