ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nico Seessle" <n...@seessle.de>
Subject Re: Repeditive Component Building
Date Sat, 02 Sep 2000 09:39:37 GMT
I'm doing something like this really successfull using the "antcall" task
like this:

    <antcall target="getAndBuild">
      <param name="build.compiler"  value="jikes"/>
      <param name="project.dir"     value="Framework/Util"/>
      <param name="project.jar"     value="v5_util1"/>
    </antcall>

As you can see (guess?) it's even possible to use different compilers for
each call.

I dont't know if this is included in the release build, but it's included in
the nightly build.

Nico

----- Original Message -----
From: "Taylor, Jeremy" <jtaylor@lehman.com>
To: <ant-user@jakarta.apache.org>
Sent: Friday, September 01, 2000 2:01 PM
Subject: RE: Repeditive Component Building


> You cannot change the value of a property once it is set. AFAIK there is
no
> way of passing parameters to a sub-task.
>
> Of course, you could always write your own optional task to do this and
then
> share it with the ANT community...
>
> > -----Original Message-----
> > From: Roy French [SMTP:rfrench@blueprinttech.com]
> > Sent: 31 August 2000 15:03
> > To: ant-user@jakarta.apache.org
> > Subject: Repeditive Component Building
> >
> > 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


Mime
View raw message