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 23595 invoked from network); 31 Aug 2000 14:04:42 -0000 Received: from unknown (HELO gatekeeper.blueprinttech.com) (root@207.91.124.57) by locus.apache.org with SMTP; 31 Aug 2000 14:04:42 -0000 Received: from TRILL (64-48-91-64.customer.algx.net [64.48.91.64]) by gatekeeper.blueprinttech.com (8.8.7/8.8.7) with SMTP id IAA17959 for ; Thu, 31 Aug 2000 08:04:23 -0600 Message-ID: <003601c01354$3b0b97d0$405b3040@gst.com> From: "Roy French" To: Subject: Repeditive Component Building Date: Thu, 31 Aug 2000 10:03:14 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0033_01C01332.AD96D610" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_0033_01C01332.AD96D610 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The end product for a project is a set of EJB jar files. While using = Ant, I find myself using the same set of tasks, only a couple of = arguments are different. After running a few tests and looking through = the Ant source code, I believe that Ant statically binds task arguments = on startup, preventing them from changing during the execution of the = build process, even if the argument contains a property. Is it possible = to define one set of tasks but have the argument values change during = the build process? Thanks Roy French ------=_NextPart_000_0033_01C01332.AD96D610 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

The end product for a project is a set = of EJB jar=20 files. While using Ant, I find myself using the same set of tasks, = only a=20 couple of arguments are different. After running a few tests and = looking=20 through the Ant source code, I believe that Ant statically binds = task=20 arguments on startup, preventing them from changing during the execution = of the=20 build process, even if the argument contains a property. Is = it=20 possible to define one set of tasks but have the argument = values change=20 during the build process?

Thanks

Roy French

------=_NextPart_000_0033_01C01332.AD96D610--