On Mon, 19 Apr 2004, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> OK, I see the problem:
I think I have a spare quarter of an hour to look into fixing it.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional command
OK, I see the problem:
In CommandlineJava#addCommandsToList(ListIterator) we have
//now any assertions are added
if (getAssertions() != null) {
getAssertions().applyAssertions(this);
}
this adds VmArgs to the CommandlineJava instance for the configured
asserti
On Mon, 19 Apr 2004, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> So CommandLineJava#getCommandline() produces a result without the
> -ea switch on the first invocation and one with the argument on the
> second.
Actually it adds -ea:AssertionTest on each invocation. If you use
multiple log statem
If you move the log statement in front of setCommandLine as in
log(cmd.describeCommand(), Project.MSG_VERBOSE);
execute.setCommandline(cmd.getCommandline());
the tests will pass but -ea: will not be part of the verbose output.
So CommandLineJava#getCommandline() produces a result
Run it with -debug instead of -verbose ...
Execute:Java13CommandLauncher: Executing
'/usr/local/java/j2sdk1.4.2_04/jre/bin/java' with arguments:
'-ea:AssertionTest'
'-classpath'
'/home/bodewig/ASF/jakarta/jakarta-ant/src/etc/testcases/types/assertions/build:/home/bodewig/junit/junit3.8.1/junit.ja
On Mon, 19 Apr 2004, Steve Loughran <[EMAIL PROTECTED]> wrote:
> I am very confused.
So am I on first glance.
If it helps a little, the problem is a cross-platform one. Happens on
my Linux box running Sun's 1.4.2_04 as well.
Stefan
-
Run test-junit in the assertions.xml test file on java1.4 :-
test-junit:
[junit] Implicitly adding
C:\Java\Apache\ant\lib\junit.jar;C:\Java\Apache\ant\lib\ant-launcher.jar;C:\Java\Apache\ant\lib\ant.jar;C:\Java\Apache\ant\lib\ant-junit.jar
to CLASSPATH
[junit] Executing 'C:\Java\JDK\jre\
