Return-Path: <donaldp@apache.org>
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 84014 invoked from network); 11 Jan 2001 15:40:19 -0000
Received: from mail.alphalink.com.au (203.24.205.7)
  by h31.sny.collab.net with SMTP; 11 Jan 2001 15:40:19 -0000
Received: from donalgar (d404-ps3-mel.alphalink.com.au [202.161.110.216])
	by mail.alphalink.com.au (8.9.3/8.9.3) with SMTP id CAA08259;
	Fri, 12 Jan 2001 02:40:21 +1100
Message-Id: <3.0.6.32.20010112022403.007e9bb0@alphalink.com.au>
X-Sender: gdonald@alphalink.com.au
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Fri, 12 Jan 2001 02:24:03 +1100
To: ant-user@jakarta.apache.org
From: Peter Donald <donaldp@apache.org>
Subject: Re: Parameterized "task-function"
Cc: ant-user@jakarta.apache.org
In-Reply-To: <3A5DCD97.32652D9A@machturtle.com>
References: 
 <EAC6539D2D64D411ADD6009027CC7BE72618E1@exchange.chicago.zefer.com>
 <3A5C59E8.A938C0A9@machturtle.com>
 <3.0.6.32.20010111175418.009fb100@alphalink.com.au>
 <3.0.6.32.20010111224217.007e6af0@alphalink.com.au>
 <3.0.6.32.20010112002309.007f2cb0@alphalink.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

At 10:13  11/1/01 -0500, David Corbin wrote:
>I do try to limit my re-invention.  But, when the architecture is
>fatally flawed, it can't just be re-written.  Maybe my understanding of
>XSLT is the thing that's fatally flawed.  Let's return to the original
>issue.  I asked about writing parameterized tasks (with a small
>reference to includes).  You said, XSLT will handle that.  Can you show
>me how?  Does it require a second file, or is it integral to the
>build.xml file?

Usually a second file thou we could make it internal aswell I believe
without too much trouble. A possible example would be (remembering that I
also hate XSLT so may have munged the syntax):

<xsl:template match="build-jar">
  <javac srcdir="src/java/{@name}" destdir="build/{@name}"/>
  <jar jarfile="{@name}.jar" basedir="build/{@name}"/>
  <signjar jarfile="{@name}.jar" />
  <cab cabfile="{@name}.cab" basedir="build/{@name}"/>
  <signcab cabfile="{@name}.cab" />
</xsl:template>

now somewherer in your build file you would have

<target name="foo">
  <build-jar name="bean1" />
  <build-jar name="bean2" />
  <build-jar name="bean3" />
</target>

This would compile, jar, cab and sign the three beans so that they are
ready for distribution via web-browser. This is just a simple example but
it could get much more complex allowing you to do virtually everything.
Kinda like some of those make builders ;) It is complex but it brings power.

Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*