Return-Path: <david.corbin@machturtle.com>
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 73482 invoked from network); 11 Jan 2001 18:07:52 -0000
Received: from machturtle.com (HELO mars.corsol.atlanta.ga.us)
 (mail@130.205.107.3)
  by h31.sny.collab.net with SMTP; 11 Jan 2001 18:07:52 -0000
Received: from metcalfe.machturtle.com (localhost) [130.205.107.2]
	by mars.corsol.atlanta.ga.us with esmtp (Exim 3.12 #1 (Debian))
	id 14GmBi-0003Bq-00; Thu, 11 Jan 2001 13:11:02 -0500
Received: from localhost ([127.0.0.1] helo=machturtle.com)
	by localhost with esmtp (Exim 3.20 #1 (Debian))
	id 14Gm8g-00017A-00
	for <ant-user@jakarta.apache.org>; Thu, 11 Jan 2001 13:07:54 -0500
Sender: dcorbin
Message-ID: <3A5DF677.FDC35FE1@machturtle.com>
Date: Thu, 11 Jan 2001 13:07:51 -0500
From: David Corbin <david.corbin@machturtle.com>
Organization: Mach Turtle Technologies
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.13 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ant-user@jakarta.apache.org
Subject: Re: Parameterized "task-function"
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>
 <3.0.6.32.20010112022403.007e9bb0@alphalink.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-via: mars.corsol.atlanta.ga.us
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Peter Donald wrote:
> 
> 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.

Well, I can live with that, IFF it is in a single file...
> 
> 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               |
> *-----------------------------------------------------*

-- 
David Corbin 		
Mach Turtle Technologies, Inc.
http://www.machturtle.com
dcorbin@machturtle.com