Seeing log output when running tests with AntUnit

Hello, I've been trying to use AntUnit and cannot see a way to view the typical Ant output of the Ant targets being tested. The only output is that which AntUnit generates, describing the tests executed, etc. If a test fails it is important to view the log of the steps that happened. Can anyone s

RE: Seeing log output when running tests with AntUnit

>It's being saved to a log where you can make assertions about >output text, using assertion, which >itself uses the the condition How would I print the content of that log? >Maybe we could tweak antunit also print the buffer on an >assertion failure, but generally I just run the target by

Should ScriptRunner call terminate() on the BSFManager?

Hi, We've recently integrated Jepp (http://jepp.sourceforge.net/) into our use of Ant via the BSF engine. This is very useful because we use Python for scripting quite a lot and it allows Python code to be used in full while also allowing access to Java objects. This has resulted in a Java OOM

RE: Should ScriptRunner call terminate() on the BSFManager?

Do I need to do anything to follow up on this? How to ensure this fix gets into a future release? thanks paul >-Original Message- >From: ext Peter Reilly [mailto:[EMAIL PROTECTED] >Sent: Tuesday, March 25, 2008 3:52 PM >To: Ant Developers List >Subject: Re: Should ScriptRunner call te

Performance of fileset related operations with a large number of files

Hello, I have been trialling Ant as a driver for a large scale build execution. The preparation before the build involves copying and unzipping >100,000 files spread across >20,000 directories. When using Ant's built in copy task with filesets selecting large parts of these files, a long time is s

# character causes problem parsing -lib paths

Hello, I have found that if I specify a -lib option with a path that contains a hash "#" character, it cannot find the libraries. Without the # character in the path they can be picked up fine. This is not easily avoided in our environment, as we use Synergy for SCM, which defaults to using # in

RE: # character causes problem parsing -lib paths

Hi Peter, >I have made a change to ant SVN to fix this. So if I wanted to get a version of Ant with it fixed I could check it out from SVN? Is there any bug fix release schedule for Ant? I'm wondering because there has not been a new release for some time. cheers paul >-Original Message

RE: # character causes problem parsing -lib paths

Hello, I have tested an SVN snapshot of Ant with the fix in for parsing # in the path. It works using Java 1.4.2 but not Java 1.3.1. My understanding is that 1.3 is intended to be supported for Ant 1.7 based on this page http://wiki.apache.org/ant/Ant17/Planning. Is it possible to test this functi

using multiple properties in the 'if' and 'unless' conditions

Hello, Has the possibility of adding multiple conditions to the target 'if' and 'unless' attributes ever been considered? Are there any reasons why this change would be a bad idea? cheers paul

conditional attributes for arg and env elements

Hello, Would it be possible to add if and unless attributes to the env and arg elements used in exec, in the same way that include and exclude elements have? This would make the use of exec more flexible. A problem that I currently have is that a script being called from Ant will check the envir