ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: Feature Request: Ant batching support
Date Wed, 07 Mar 2001 18:48:12 GMT
I haven't actually written them yet. I have already modified the Ant 
and Project objects, tho, so I think I can get by until something else 
comes out...

The idea is to allow a template file equal access as the main build 
file to some environment.xml file that sets up tagdefs, file 
availability, and other properties, etc. Then, any of these files may 
be run in order to compile/run/junit test/etc. any specific package.  
The only alternative I've come up with is to make a shell script that 
sets a -D property and a target within the main build.xml file to 
direct the appropriate file to be executed...however, this means I now 
have a set of shell scripts that I have to port between Unix and 

So far, I haven't heard any way to fully initialize an Ant session via 
some external (and equally accessible) source.  This is simply an 
object-oriented approach to the use of Ant, and I see this as 
imperative to maintaining this project's build structure in the future. 
 If there is another way to read an external source (or equivalent), 
and set tagdefs, available's, uptodate's, and properties, then please 
let me know.  If not, please consider enabling this approach...

I don't mean to be confrontational, I'm just not sure how I can be 
clearer about what I need...

Thanks for the help,
John Casey

-----Original Message-----
From: holtdl []
Sent: Wednesday, March 07, 2001 11:01 AM
To: ant-dev
Cc: holtdl
Subject: RE: Feature Request: Ant batching support


First let me say, I'm not trying to quash your feature requests, just
trying to help you out in the meantime.

I've looked at the files you sent earlier, and I think you can probably
work within what's currently available, but can you send a sample of one
of your sub-project build files?


--- wrote:
> I would hesitate to make the child call a target on the parent, if 
> that's what you mean, because it's not self-contained, and references 
> outside of the file could become very confusing to one trying to 
> the flow of the build.
> John
> -----Original Message-----
> From: sbailliez []
> Sent: Wednesday, March 07, 2001 10:26 AM
> To: ant-dev
> Cc: sbailliez
> Subject: RE: Feature Request: Ant batching support
> > -----Original Message----- 
> > From: Stefan Bodewig [] 
> [...] 
> > > Also: I'd like the ability to specify <ant keepenv="true"...>, or 
> > > something like this, in order to preserve the environment of the 
> > > child project into the parent's.  This would be useful in setting 
> > > common build environment from many build.xml files, 
> > 
> > It seems to me as if including (either with entities as in the FAQ 
> > via a new Ant specific include mechanism) would be the cleaner 
> > solution for your problem. Probably I am missing something. 
> What do you think about target and or project inheritance ? :) 
> -- 
>  St├ęphane Bailliez 
>  Software Engineer, Paris - France 
>  iMediation - 
>  Disclaimer: All the opinions expressed above are mine and not those 
> from my company. 
> > 
> To unsubscribe, e-mail:
> For additional commands, e-mail:


Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message