Return-Path: 
 <ant-user-return-24631-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 23300 invoked from network); 5 Sep 2002 16:34:41 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 5 Sep 2002 16:34:40 -0000
Received: (qmail 7067 invoked by uid 97); 5 Sep 2002 16:34:46 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 7012 invoked by uid 97); 5 Sep 2002 16:34:45 -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 6993 invoked by uid 98); 5 Sep 2002 16:34:44 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: <foreach> & <propertycopy> (was 'RE: Automated source config model?')
Date: Thu, 5 Sep 2002 12:22:29 -0400
Message-ID: <9093431B64301C47986EF078512912AD591326@xchange.stargus.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Automated source config model?
Thread-Index: AcJUWn2jxlMBCWBvSZy3WeNtbzYvRAAkOo2A
From: "Matt Lyon" <matt@stargus.com>
To: "Ant Users List" <ant-user@jakarta.apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

DD,

Thanks for the information! The issue I was facing seemed to be due to =
property scope/flow control. I had placed a task to read in properties =
from an external properties file inside an init target, which did not =
allow the subsequent targets to work the <propertycopy> magic of =
expanding nested properties in that same property file which you so =
eloquently described. If I place the  <property =
file=3D"config.properties"/> at the <project> level in my buildfile and =
not inside any target, that gets me past the problem.

However, I'm still stuck on a <propertycopy> issue. Using Matt McHenry's =
model again, if I have an external properties file that lists the =
following:

#The list of modules
components=3Dplatform,ui,content

#The tag for the 'platform' module
platform.tag=3DV1_0_6_183
#The platform directories
platform.dirs=3Dstarman/src/com/stargus/platform

#The tag for the 'ui' module
ui.tag=3DV1_0_6_183
#The ui directories
ui.dirs=3Dstarman/src/com/stargus/web,starman/src/web

#The tag for the 'content' module
content.tag=3DV1_0_7_184
#The content directories
content.dirs=3Dstarman/src/com/stargus/platform/content

And a build.xml which contains the following target sequence:

  <!-- Targets to check out the souce code from CVS. -->=20
  <target name=3D"checkout"=20
          depends=3D"init"=20
          description=3D"Checks out tagged directories listed in the =
build_config.properties file.">
    <foreach list=3D"${components}"
             target=3D"checkout-dirs"
             param=3D"component"/>
  </target>

  <target name=3D"checkout-dirs">=20
    <propertycopy name=3D"complist"
                  from=3D"${component}.dirs"/>
    <propertycopy name=3D"comptag"
                  from=3D"${component}.tag"/>
    <foreach list=3D"${complist}"
             target=3D"checkout-dir"
             param=3D"ckout.pkg"/>
  </target>

  <target name=3D"checkout-dir-tag"
          if=3D"comptag">
    <echo message=3D"checking out ${ckout.pkg} with tag ${comptag}"/>
    <cvs cvsRoot=3D"${cvsRoot}"
         dest=3D"${src}"
         command=3D"co -P -r ${comptag} ${ckout.pkg}"/>
  </target>=20

  <target name=3D"checkout-dir-notag"=20
          unless=3D"comptag">
    <echo message=3D"NOTE: no tag defined for ${ckout.pkg}; checking out =
from main code line"/>=20
    <cvs cvsRoot=3D"${cvsRoot}"
         dest=3D"${src}"
         command=3D"co -PA ${ckout.pkg}"/>
  </target>

  <target name=3D"checkout-dir" =
depends=3Dcheckout-dir-tag,checkout-dir-no-tag"/>


What I'm finding is that the ${complist} property value is passed to the =
checkout-dir tag as param ${ckout.pkg} with the expected <foreach> =
iterations performed, but the checkout-dir-tag target is never executed =
because the ${comptag} property value is either not getting defined by =
<propertycopy> or is not recognized by the checkout-dir composite target =
due to some sort of flow control or property scope issue. How can I =
force the setting and propagation of the ${comptag} property value to =
the subsequent targets?

Matt
-----Original Message-----
From: Dominique Devienne [mailto:DDevienne@lgc.com]
Sent: Wednesday, September 04, 2002 5:43 PM
To: 'Ant Users List'
Subject: RE: Automated source config model?


The <foreach> sets the 'component' param (not property, but the =
distinction
is small), passed to the 'checkout-dirs' target. This target in turn =
doesn't
use the 'component.dirs' property, it uses the 'component' property, to
lookup the '${component}.dirs' property, where ${component} is resolved =
to
its value (for example, acme.dirs). This is the bit of magic =
<propertycopy>
does, allowing nested properties (it's equivalent to the illegal
${${component}.dirs}).

I don't thing this has anything to do with property immutability.

Hope this helps. --DD

-----Original Message-----
From: Matt Lyon [mailto:matt@stargus.com]=20
Sent: Wednesday, September 04, 2002 4:19 PM
To: Ant-User (E-mail)
Subject: RE: Automated source config model?

Matt,
=20
Thanks for the information. What I don't understand about your approach =
is
how the foreach task in your checkout target can pass a param to the
propertycopy task to define the value which it is supposed to then =
associate
with the matching property value in from the propfile to create a new
property. Specifically, I'm referring to
=20
  <!-- targets to check out the souce code from cvs -->=20
  <target name=3D"checkout" depends=3D"init"=20
          description=3D"checks out tagged directories listed in the
propfile">=20
    <record name=3D"${cvslogfile}" append=3D"true" action=3D"start"/>=20
    <foreach list=3D"${components}" target=3D"checkout-dirs" =
param=3D"component"/>
=20
^
    <antcall target=3D"checkout-build" inheritAll=3D"true"/>=20
    <record name=3D"${cvslogfile}" action=3D"stop"/>=20
  </target>=20
=20
and=20

  <target name=3D"checkout-dirs">=20
    <propertycopy name=3D"complist" from=3D"${component}.dirs"/>
                                                         ^
    <propertycopy name=3D"comptag" from=3D"${component}.tag" =
silent=3D"true"/>=20
    <foreach list=3D"${complist}" target=3D"checkout-dir" =
param=3D"ckout.pkg"/>=20
  </target>=20
=20
There's probably a really simple explanation, but I'm missing something
conceptually here. If I try something similar my build bombs out because =
the
value of ${component.dirs} is not defined for the checkout-dirs target. =
Is
this due to property immutability holes being plugged in Ant 1.5?
=20
Matt

-----Original Message-----
From: McHenry, Matt [mailto:mmchenry@carnegielearning.com]
Sent: Tuesday, September 03, 2002 5:07 PM
To: Matt Lyon
Cc: Ant Users List
Subject: RE: Automated source config model?



> Thanks for the information. I would be interested in seeing how you
implemented what you have if > you can give me a high level view without
ruffling any feathers. Thanks.

        Okay, here's an example java properties file that defines a set =
of
deliverables built from several components, each checked out from CVS =
with a
different tag.

        (This is a bit more than what you want, as it's geared towards
checking out into a sandbox directory where the build happens, then
collecting all the deliverables into a holding directory so that the
installer project can find them.)


#the deliverable files=20
deliverables.files=3Ddist/lib1.jar,dist/lib2.jar=20

#you can also specify entire directories=20
#deliverables.dirs=20

#the list of components -- details of each are specified below=20
components=3Dplatform,ui,content=20

#the buildfile=20
build.file=3Dbuild.xml=20
build.file.tag=3DBUILDFILE_03=20
build.dir=3Dsrc=20
build.target=3Djars=20

#the tag for the 'platform' component=20
platform.tag=3DPLATFORM_17=20
#the directories under CVS covered by that tag=20
platform.dirs=3Dsrc/platform,src/foo=20

#the tag for the 'ui' component=20
ui.tag=3DUI_08=20
#the directories under CVS covered by that tag=20
ui.dirs=3Dsrc/ui,src/util=20

#leave the tag undefined to check out=20
#to the edge of the main trunk=20
#content.tag=3D=20
content.dirs=3Dcontent/site1,content/site1,content/site3=20

        The following ant project will process this sort of properties =
file.
You can just use the 'checkout' target to pull stuff from CVS, or if you
also want to build according to the build.* properties, you can use the
'call-build' or 'copy-delivs' targets.


<project name=3D"cvsbuild" default=3D"copy-delivs" basedir=3D".">=20

  <!-- This ant file defines targets used to check out code and a=20
  build file from CVS, call a target in that build file, and copy the=20
  deliverables created by that build file into a deliverables=20
  directory.  The build file can also be left out if all of the=20
  deliverables are retrieved directly from CVS.  This is useful for=20
  e.g. straight text files, or third-party binaries.=20

  When using this ant file, the property 'propfile' must be defined on=20
  the command line (e.g. ant -Dpropfile=3Djava-tags.txt).  This property =

  is the name of an ant properties file.  The propfile is basically a=20
  list of CVS modules, and tags corresponding to one or more of the=20
  modules.=20

  For a given tagged module, two properties should be defined:=20
   <module>.tag: the cvs tag for this module=20
   <module>.dirs: a comma-separated list of directories which make up=20
                  this module=20
  The <module>.tag property may be left undefined, in which case the=20
  module will be checked out to the edge of the tree.=20

  The propfile must define the following special property:=20
   components: a comma-separated list of the <module> tags to be used=20
               in the build.=20

  At least one of these two properties must be defined as well:=20
   deliverables.files: a comma-separated list of paths to individual=20
                       deliverable files (typically .zip files)=20
   deliverables.dirs: a comma-separated list of paths to deliverable=20
                      directories.  This is used to pull an entire=20
                      directory out of CVS into the deliverables=20
                      directory.=20

  If the deliverables must be constructed via a buildfile, the=20
  propfile should define the following four special properties:=20
   build.file: the name of the ant build file for this project.  The=20
               path to this file is constructed as=20
               ${build.dir}/${build.file}.=20
   build.dir: the base directory to use when calling ant using=20
              ${build.file}.=20
   build.target: the name of the target (defined in ${build.file}) to=20
                 build=20
   build.file.tag: the cvs tag to use when checking out the build=20
                   file.=20
  The build.file.tag property may be left undefined, in which case the=20
  build file will be checked out to the edge of the tree.=20

  This ant file also defines a target to tag the modules listed in a=20
  propfile.  Typically this is used once a build (the copy-delivs=20
  target) has succeeded to mark the source code as stable & as part of=20
  whatever release is being built.=20

  -->=20

  <taskdef name=3D"foreach"=20
           =
classname=3D"org.apache.tools.ant.taskdefs.optional.ForEach"/>=20
  <taskdef name=3D"propertycopy"=20
           =
classname=3D"org.apache.tools.ant.taskdefs.optional.PropertyCopy"/>


  <!-- the temporary directory where we'll check out the modules -->=20
  <property name=3D"cvstree" value=3D"${basedir}/cvstree"/>=20

  <!-- the directory where the deliverables will be stored -->=20
  <property name=3D"deliv.dir" value=3D"${basedir}/deliv"/>=20

  <!-- file where cvs actions are logged -->=20
  <property name=3D"cvslogfile" value=3D"cvslog"/>=20

  <!-- file where the results of building target ${build.target} in=20
  ${build.file} are logged -->=20
  <property name=3D"buildlogfile" value=3D"buildlog"/>=20

  <!-- load in the properties from the propfile -->=20
  <property file=3D"${propfile}"/>=20


  <target name=3D"check-for-tagname" unless=3D"tagname"=20
          description=3D"checks that the 'tagname' property has been =
defined">

    <echo message=3D"You must define the 'tagname' property on the =
command
line.  For example:"/>=20
    <echo message=3D"   ant -Dtagname=3DSTABLE_2002"/>=20
    <fail message=3D"The 'tagname' property has not been defined."/>=20
  </target>=20

  <target name=3D"check-for-propfile"=20
          description=3D"checks that the file 'propfile' exists">=20
    <available file=3D"${propfile}" type=3D"file" =
property=3D"propfile-ok"/>=20
    <antcall target=3D"fail-no-propfile"/>=20
  </target>=20

  <target name=3D"fail-no-propfile" unless=3D"propfile-ok"=20
          description=3D"presents an error message to the user if =
'propfile'
is invalid">=20
    <echo message=3D"You must define the 'propfile' property on the =
command
line.  For example:"/>=20
    <echo message=3D"   ant -Dpropfile=3Dtags.txt"/>=20
    <echo message=3D"will build according to the tags in the file =
tags.txt"/>=20
    <fail message=3D"The 'propfile' property has not been defined, or =
points
to a non-existent file."/>=20
  </target>=20

  <target name=3D"init" depends=3D"check-for-propfile">=20
    <mkdir dir=3D"${cvstree}"/>=20
  </target>=20


  <!-- targets to check out the souce code from cvs -->=20
  <target name=3D"checkout" depends=3D"init"=20
          description=3D"checks out tagged directories listed in the
propfile">=20
    <record name=3D"${cvslogfile}" append=3D"true" action=3D"start"/>=20
    <foreach list=3D"${components}" target=3D"checkout-dirs" =
param=3D"component"/>

    <antcall target=3D"checkout-build" inheritAll=3D"true"/>=20
    <record name=3D"${cvslogfile}" action=3D"stop"/>=20
  </target>=20

  <!-- WARNING: this depends on init, but it should only be called by=20
  the checkout wrapper task, so we're going to leave the explicit=20
  dependency off for efficiency -->=20
  <target name=3D"checkout-build" if=3D"build.file">=20
    <propertycopy name=3D"comptag" from=3D"build.file.tag" =
silent=3D"true"/>=20
    <antcall target=3D"checkout-dir" inheritAll=3D"true">=20
      <param name=3D"ckout.pkg" value=3D"${build.dir}/${build.file}"/>=20
    </antcall>=20
  </target>=20

  <!-- WARNING: this depends on init, but it should only be called by=20
  the checkout wrapper task, so we're going to leave the explicit=20
  dependency off for efficiency -->=20
  <target name=3D"checkout-dirs">=20
    <propertycopy name=3D"complist" from=3D"${component}.dirs"/>=20
    <propertycopy name=3D"comptag" from=3D"${component}.tag" =
silent=3D"true"/>=20
    <foreach list=3D"${complist}" target=3D"checkout-dir" =
param=3D"ckout.pkg"/>=20
  </target>=20

  <!-- WARNING: this depends on init, but it should only be called by=20
  the checkout-dirs wrapper task, so we're going to leave the explicit=20
  dependency off for efficiency -->=20
  <target name=3D"checkout-dir-tag" if=3D"comptag">=20
    <echo message=3D"checking out ${ckout.pkg} with tag ${comptag}"/>=20
    <cvs dest=3D"${cvstree}" quiet=3D"true" failonerror=3D"true"=20
         command=3D"checkout -P -r ${comptag} =
&quot;${ckout.pkg}&quot;"/>=20
  </target>=20

  <!-- WARNING: this depends on init, but it should only be called by=20
  the checkout-dirs wrapper task, so we're going to leave the explicit=20
  dependency off for efficiency -->=20
  <target name=3D"checkout-dir-notag" unless=3D"comptag">=20
    <echo message=3D"NOTE: no tag defined for ${ckout.pkg}; checking out =
to
edge of tree"/>=20
    <cvs dest=3D"${cvstree}" quiet=3D"true" failonerror=3D"true"=20
         command=3D"checkout -PA &quot;${ckout.pkg}&quot;"/>=20
  </target>=20

  <target name=3D"checkout-dir"
depends=3D"checkout-dir-tag,checkout-dir-notag"/>=20


  <!-- targets to tag the souce code in cvs -->=20
  <target name=3D"tag" depends=3D"init,check-for-tagname"=20
          description=3D"tags directories listed in the propfile">=20
    <record name=3D"${cvslogfile}" append=3D"true" action=3D"start"/>=20
    <foreach list=3D"${components}" target=3D"tag-dirs" =
param=3D"component"/>=20
    <antcall target=3D"tag-build" inheritAll=3D"true"/>=20
    <record name=3D"${cvslogfile}" action=3D"stop"/>=20
  </target>=20

  <!-- WARNING: this depends on init, but it should only be called by=20
  the tag wrapper task, so we're going to leave the explicit=20
  dependency off for efficiency -->=20
  <target name=3D"tag-build" if=3D"build.file">=20
    <antcall target=3D"tag-dir" inheritAll=3D"true">=20
      <param name=3D"ckout.pkg" value=3D"${build.dir}/${build.file}"/>=20
    </antcall>=20
  </target>=20

  <!-- WARNING: this depends on init, but it should only be called by=20
  the tag wrapper task, so we're going to leave the explicit=20
  dependency off for efficiency -->=20
  <target name=3D"tag-dirs">=20
    <propertycopy name=3D"complist" from=3D"${component}.dirs"/>=20
    <foreach list=3D"${complist}" target=3D"tag-dir" =
param=3D"ckout.pkg"/>=20
  </target>=20

  <!-- WARNING: this depends on init, but it should only be called by=20
  the tag-dirs wrapper task, so we're going to leave the explicit=20
  dependency off for efficiency -->=20
  <target name=3D"tag-dir">=20
    <echo message=3D"tagging ${ckout.pkg} with tag ${tagname}"/>=20
    <cvs dest=3D"${cvstree}" quiet=3D"true" failonerror=3D"true"=20
         command=3D"tag -F ${tagname} &quot;${ckout.pkg}&quot;"/>=20
  </target>=20


  <!-- a target to call out to the build.xml we've gotten out of CVS --> =

  <target name=3D"call-build-bf" depends=3D"init,checkout" =
if=3D"build.file"=20
          description=3D"executes the selected target on the checked-out =
build
file">=20
    <record name=3D"${buildlogfile}" append=3D"true" action=3D"start"/>=20
    <echo message=3D"calling target ${build.target} in buildfile
${build.dir}/${build.file}"/>=20
    <ant antfile=3D"${build.file}" dir=3D"${cvstree}/${build.dir}"
target=3D"${build.target}" inheritAll=3D"false"/>=20
    <record name=3D"${buildlogfile}" action=3D"stop"/>=20
  </target>=20

  <target name=3D"call-build-nobf" unless=3D"build.file"=20
          description=3D"makes a note in the log file that no build file =
is
being called">=20
    <echo message=3D"NOTE: No build file is defined, so no call to it is =
being
made."/>=20
    <echo message=3D"      Deliverables are assumed to have been checked =
out
directly from CVS."/>=20
  </target>=20

  <target name=3D"call-build" depends=3D"call-build-bf,call-build-nobf"=20
          description=3D"meta-target to call out to a build file, if one =
is
defined"/>=20

  <!-- targets to copy the deliverables to where they belong -->=20
  <target name=3D"init-deliv" description=3D"creates the 'deliv.dir' =
directory">

    <mkdir dir=3D"${deliv.dir}"/>=20
  </target>=20

  <target name=3D"copy-delivs"
depends=3D"call-build,init-deliv,copy-deliv-files,copy-deliv-dirs"=20
          description=3D"meta-target to copy the deliverables"/>=20

  <target name=3D"copy-deliv-files" if=3D"deliverables.files"=20
          description=3D"copies each of the deliverable files">=20
    <foreach list=3D"${deliverables.files}" target=3D"copy-deliv-file"
param=3D"deliv"/>=20
  </target>=20

  <target name=3D"copy-deliv-dirs" if=3D"deliverables.dirs"=20
          description=3D"copies each of the deliverable directories">=20
    <foreach list=3D"${deliverables.dirs}" target=3D"copy-deliv-dir"
param=3D"deliv"/>=20
  </target>=20

  <target name=3D"copy-deliv-file">=20
    <echo message=3D"copying deliverable file(s): ${deliv}"/>=20
    <copy todir=3D"${deliv.dir}" flatten=3D"true">=20
      <fileset dir=3D"${cvstree}">=20
        <include name=3D"${deliv}"/>=20
      </fileset>=20
    </copy>=20
  </target>=20

  <target name=3D"copy-deliv-dir">=20
    <echo message=3D"copying deliverable dir(s): ${deliv}"/>=20
    <copy todir=3D"${deliv.dir}/${deliv}" flatten=3D"false">=20
      <fileset dir=3D"${cvstree}/${deliv}"/>=20
    </copy>=20
  </target>=20


  <!-- housekeeping targets -->=20
  <target name=3D"clean-comps" depends=3D"init"=20
          description=3D"removes all checked-out components from the =
temporary
cvs tree, including the build file">=20
    <foreach list=3D"${components}" target=3D"clean-dirs" =
param=3D"component"/>=20
    <antcall target=3D"clean-buildfile" inheritAll=3D"true"/>=20
  </target>=20

  <target name=3D"clean-buildfile"=20
          description=3D"removes the checked-out build file">=20
    <echo message=3D"deleting file ${build.dir}/${build.file}"/>=20
    <delete file=3D"${cvstree}/${build.dir}/${build.file}"/>=20
  </target>=20

  <target name=3D"clean-dirs">=20
    <propertycopy name=3D"complist" from=3D"${component}.dirs"/>=20
    <foreach list=3D"${complist}" target=3D"clean-dir-or-file"
param=3D"clean.pkg"/>=20
  </target>=20

  <target name=3D"decide-dir-or-file">=20
    <available file=3D"${cvstree}/${clean.pkg}" type=3D"dir"
property=3D"tgt-is-dir"/>=20
  </target>=20

  <target name=3D"clean-dir" if=3D"tgt-is-dir">=20
    <echo message=3D"deleting directory ${clean.pkg}"/>=20
    <delete dir=3D"${cvstree}/${clean.pkg}"/>=20
  </target>=20

  <target name=3D"clean-file" unless=3D"tgt-is-dir">=20
    <echo message=3D"deleting file ${clean.pkg}"/>=20
    <delete file=3D"${cvstree}/${clean.pkg}"/>=20
  </target>=20

  <target name=3D"clean-dir-or-file"
depends=3D"decide-dir-or-file,clean-dir,clean-file"/>=20

  <target name=3D"clean-delivs-dirs" if=3D"deliverables.dirs">=20
    <foreach list=3D"${deliverables.dirs}" target=3D"clean-delivs-dir"
param=3D"dir"/>=20
  </target>=20

  <target name=3D"clean-delivs-dir">=20
    <echo message=3D"deleting dir ${dir}"/>=20
    <delete dir=3D"${cvstree}/${dir}"/>=20
  </target>=20

  <target name=3D"clean-delivs-files" if=3D"deliverables.files">=20
    <foreach list=3D"${deliverables.files}" target=3D"clean-delivs-file"
param=3D"file"/>=20
  </target>=20

  <target name=3D"clean-delivs-file">=20
    <echo message=3D"deleting file ${file}"/>=20
    <delete dir=3D"${cvstree}/${file}"/>=20
  </target>=20

  <target name=3D"clean-delivs"
depends=3D"init,clean-delivs-dirs,clean-delivs-files"=20
          description=3D"removes all deliverables from the temporary cvs
tree"/>=20

  <target name=3D"clean" description=3D"removes the entire temp cvs =
tree">=20
    <delete dir=3D"${cvstree}"/>=20
  </target>=20

</project>=20


Matt McHenry=20
Software Developer=20
Carnegie Learning=20
(412)690-2442 x150=20


--
To unsubscribe, e-mail:   =
<mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: =
<mailto:ant-user-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>