ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: Could Ant build scripts be compiled?
Date Tue, 25 Nov 2003 17:13:42 GMT
My first idea was creating an executable JAR file. All property value,
build scenario and needed files (especially Ant classes) are built in.
So a simple  "java -jar mybuild.jar"  would start the default target.

But a "java -jar mybuild.jar target1 -Dprop=value"  should also be possible.

If there are interests I can translate my (old) notices (or send in German).


Serialisation of the project object was one idea, also. But that class is 
sometimes modified and I donĀ“t know whether you can load "old" files ...

So another idea was streaming to xml using xml-binding ... but I had xml
already :-)

Is XML-Binding faster that SAX? I think no. AFAIK binding is build on top of


> -----Original Message-----
> From: Stirling, Scott []
> Sent: Tuesday, November 25, 2003 5:55 PM
> To: Ant Users List
> Subject: RE: Could Ant build scripts be compiled?
> > From: Matt Benson []
> > 
> > Wouldn't it be easiest to add "implements
> > Serializable" as far down the object hierarchy as
> > possible, then add a command-line option to Main to
> > serialize the Project to a specified file instead of
> > executing targets?  Or clone Main if you wanted to
> > keep it out of Ant proper?
> Yes.  It sounds do-able.  It would be interesting to 
> prototype.  Main would need to be modified to load a 
> serialized Project too.
> I liked Jan's email.  Very off-the-cuff and funny.
> As Simon said, with enough lines of code you can do anything. 
>  There could be some other ways to do this, but probably not 
> without some more interesting changes to the Ant runtime.  A 
> related but different question is: if build scripts were 
> compiled classes, could the Ant execution engine take 
> advantage of it in more ways than by-passing the XML parsing? 
>  I'm thinking "no," but, maybe I need a cup of coffee. ;->
> Scott Stirling
> Workscape, Inc.
> **************************************************************
> *********
> This message is intended only for the use of the intended 
> recipient and
> may contain information that is PRIVILEGED and/or 
> are not the intended recipient, you are hereby notified that any use,
> dissemination, disclosure or copying of this communication is strictly
> prohibited.  If you have received this communication in error, please
> destroy all copies of this message and its attachments and notify us
> immediately.
> **************************************************************
> *********
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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