ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ultra Funkular <funku...@nettaxi.com>
Subject Re: AntStructure differences between api and buildfile usage
Date Wed, 19 Jun 2002 14:48:48 GMT
Stefan,

Thank you very much.  Calling project.init() within the api did the 
trick.  No need to generate a buildfile and read it in (slow mo), or 
define taskdefs.


Regards,


T Master



On Wed, 19 Jun 2002 02:11:37 Stefan Bodewig wrote:
> On Tue, 18 Jun 2002, Ultra Funkular <funkular@nettaxi.com> wrote:
> > Stephen Bodewig (and anyone else),
> 
> That would be Stefan, not Stephen.
> 
> > The output file of the antstructure task varies hugely depending on
> > how it was invoked.
> 
> Well, it generates output for all tasks and types defined in the
> project it is part of.  The way you invoke it, there aren't any tasks
> defined.
> 
> You may want to call Project#init before running your AntStructure
> task - init will autoload all built-in and optional task definitions
> (as long as ant.jar and optional.jar are on your classpath).
> 
> Stefan
> 
> 

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


Mime
View raw message