The idea is to support drop-in build files for inside the package
structure that will function independently of the top-level build.xml
as well as working within that file. This will support building only a
certain component or component set, without modification of the
top-level file. There are other, less elegant ways to do this, but the
consequence is more information to be transferred to the next person
supporting builds. I want ant to be a free-standing tool insofar as it
may be, and not need things like batch files or system properties
passed into the process in order for it to work.
Thanks,
John
-----Original Message-----
From: holtdl [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 06, 2001 2:27 PM
To: ant-user
Cc: holtdl
Subject: RE: Re: Ant call doesn't use same environment space.
--- [EMAIL PROTECTED] wrote:
> basically, I'm running a bunch of <available>'s, and also some
> <taskdef>'s...I need to find out what's in the source tree, and
enable
> some homespun taskdefs.
Is there a reason why you need to do those things in the sub files
instead
of the top-level one?
Diane
> -----Original Message-----
> From: holtdl [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2001 12:16 PM
> To: ant-user
> Cc: holtdl
> Subject: Re: Ant call doesn't use same environment space.
>
>
> --- [EMAIL PROTECTED] wrote:
> > In the project I'm currently working on, it would be useful to be
> able
> > to have several build.xml's reference a single build.xml thru the
Ant
> > task in order to set up the build environment, and check for
> necessary
> > files, etc. However, when I create a scenario like this, I find
that
> > the environment changes accomplished in the sub-call aren't
> propagated
> > to the environment at large. Is it possible to set a flag to save
> these
> > changes? If not, would it be feasible to change the Ant taskdef to
do
> > this? I think I know how to do so, and don't mind volunteering my
> time
> > to get this functionality.
>
> Hi John,
>
> Can you say more about what's getting set in the sub files that you'd
> want
> propagated throughout the build? You -can- propagate property values
> using the <ant> task, but I'd need to know more about what you're
> actually
> wanting to do before I could offer up specific advice.
>
> Diane
>
> =====
> ([EMAIL PROTECTED])
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
>
=====
([EMAIL PROTECTED])
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
