Luc Maisonobe wrote:
Lee, Howard a écrit :
Hi Luc,
Sorry about the late reply. Have been out of town. I'm enclosing the ant test
output file. I'm using old ant (I don't know if that makes difference in this
case. Using 1.6.5) and using Junit 4.4. Looking forward to official release! :)
Thanks!
All failing tests in this log file follow the same pattern:
[junit] Running org.apache.commons.math.xxx.YyylTest
[junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0 sec
[junit] Testsuite: org.apache.commons.math.xxx.YyylTest
[junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0 sec
[junit] Testcase: warning took 0 sec
[junit] FAILED
[junit] No tests found in org.apache.commons.math.xxx.YyylTest
[junit] junit.framework.AssertionFailedError: No tests found in
org.apache.commons.math.xxx.YyylTest
This seems to correspond exactly to the Junit 4 tests. The Junit 3 tests
do pass correctly.
Perhaps your version of ant does not like a mix of Junit 3 and Junit 4
tests ? Are you sure junit 4 is used and there is no junit 3 hidden in
your ant installation ? Is it possible to force ant to use junit 4 ?
It is already being forced to use junit 4. The Ant build first looks at
build.properties (if it exists), then /usr/share/junit for junit-4.4.jar
and if it does not find it, downloads from repo1 (as it did in Howard's
case), so it is definitely using Junit 4.4. Looks like the problem is
compatability of the Ant junit task in Ant 1.6.5 with Junit 4.
Phil
Luc
-----Original Message-----
From: Luc Maisonobe [mailto:[email protected]]
Sent: Saturday, July 25, 2009 10:11 AM
To: Commons Users List
Subject: Re: Building commons-math.jar
Phil Steitz a écrit :
Luc Maisonobe wrote:
Lee, Howard a écrit :
Hi Luc,
There's no text or xml log files in the target directory. What would
be the name? I just ran "ant jar" command. Thanks for the snap shot.
We no< use maven 2 rather than ant to build commons-math. The ant
built has not been updated for a while and I even though we have
removed it completely ... I guess this could explain both the
failures and the lack of files in the target directory.
No, the Ant build should still work and does work4me at least on jdk
1.6 and 1.5. The test failures should show up in the Ant stdout
output. It would be good to know what they are/were, as the Ant build
is running the same tests tht the maven build is.
You are right.
I checked the test using ant and they also run correctly and automatically use
the complete test suite. Ant does not store the tests results nor set up the
reports maven does, which seems normal to me. It only creates the classes and
test-classes directories in target.
Lee, could you try again and store the output from the "ant test"
command and send us the extract that shows the failing tests ?
Luc
Phil
---------------------------------------------------------------------
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]
**********************************************************************
E-mail sent through the Internet is not secure. Western Asset
therefore recommends that you do not send any confidential or
sensitive information to us via electronic mail, including social
security numbers, account numbers, or personal identification
numbers. Delivery, and or timely delivery of Internet mail is not
guaranteed. Western Asset therefore recommends that you do not send
time sensitive or action-oriented messages to us via electronic
mail.
**********************************************************************
------------------------------------------------------------------------
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
