ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bemowski, Paul A" <>
Subject RE: Ant and IDL compilers ?
Date Tue, 08 Aug 2000 16:31:16 GMT

Whether you exec it, or use a custom task to do it in process, you have to
compile everything every time.  The only way around it is to parse into the
idl and know the output format of the idl2java command.  A file like foo.idl
could generate hundreds of .java files with nothing to do with the word foo.

With java and rmi for instance you know that cranked
thru javac and rmic will produce CustomerService_Stub.class, and you can
check for the existence and timestamp of the CustomerService_Stub.class.
You did all that just by file naming conventions.  Unless they are self
imposed, idl has no such restrictions, so there is no way to deal with it
without parsing into foo.idl to find out what it should be generating.


-----Original Message-----
From: Bruce Cohen []
Sent: Tuesday, August 08, 2000 12:05 PM
Subject: Re: Ant and IDL compilers ?

For those of you using exec to call 'idl2java', How do you
determine if the source is out of date with
respect to the IDL file?  Or are you always generating
source even if its not out of date?


------Original Message------
From: (Michael Haertjens)
Sent: August 8, 2000 1:48:41 PM GMT
Subject: Re: Ant and IDL compilers  ?

Markus Kohler wrote:
> Hi,
> Does anyone working with Ant and an (Corba)IDL compiler ?
> What is your approach to call the idl compiler ?
> Regards,
> Markus

Using an exec command:

<target name="idl2java" depends="init, generate_idl">
command="idl2java -root_dir ${catalyst.home} -no_tie -no_examples
-package=com.modusoperandi.catalyst.server.Person ${basedir}/*.idl"

Hope this helps

Michael Haertjens
Dreamer, Shaper, Singer, Maker.

Systems Engineer

FREE Personalized Email at
Sign up at

View raw message