Gayan, you can redirect the console output to a file using something like this:
ant ... -v >log.txt In the log.txt file will be the console output from running the command. Open it with a text editor and you will see the whole command as requested. HTH Bill -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 6:37 AM To: Ant Users List Subject: Re: FW: problem with using fork in windows xp Gayan Asanka wrote: > Hi Steve, > > I can't observe all the output with this codes. Because it consumes > hell a lot of classpaths. Only the final part I can read via my > command prompt window. So I will try a small program that doesn't use > any big jars, and simulate the error in small scale. Then I will be > able to give you something (if there is) maybe tomorrow. This is all I > can observe:- > well, whatever the problem is, it is in that claspath. You could always JAR your code before you run the unit tests against the JAR. I know that is at odds with the "only jar if the tests pass" rule, but Iike this because it tests your JAR code too. And it keeps the class shorter. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
