ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mariusz Nowostawski <mari...@marni.otago.ac.nz>
Subject Re: [PATCH] exec with include/exclude
Date Fri, 26 May 2000 23:50:29 GMT
I have not checked that on windows, I run simple tests locally here on
Linux only, but I suspect it should work on both the same. 
If your target looks something like this:

<target name="idls">
    <exec dir="."
          command="jidl --output-dir classes --package com.my.idl"
          src="idls" output="out.txt"/>
</target>

and inside ./idls you have your *.idl sources:
0. Invoke: ant idls
1. Check what you have after execution of the idls target inside out.txt;
   in normal conditions this file should be empty, but if your jidl has
   any troubles you can get the idea whats wrong from out.txt
2. Make sure the output dir is already created (jidl I am using will
   simply fail if you do not have output directory already created)
3. If you still cannot guess whats wrong, show me your out.txt file, your
   target and what ant is printing out when you executing idls target

--
As I said, I am using Linux, and I have not noticed any troubles here,
with target like the one above, with jidl being ORBacus 3.1.3, I have:
  my out.txt is empty, 
  ant is printing:

$ ant idls

Buildfile: build.xml
Project base dir set to: /home/mariusz/Projects/nzdis/oql
Executing Target: idls
[exec] jidl --output-dir classes --package com.my.idl in /home/mariusz/Projects/nzdis/oql
for 3 files.
Completed in 1 seconds

  and inside classes/com/my/idl/* I have the expected java sources written
correctly to disk.  I have not checked that on windows though.. 


hope it helps
Mariusz


> I tried the patch and find the jidl program opens up a bunch of command
> windows on NT and although jidl appears to process the idl files,
> nothing is written to disk.
> 
> Dave



Mime
View raw message