Curt Arnold wrote:
On Mar 15, 2006, at 12:59 PM, Bill Barker wrote:
-----Original Message-----
From: Curt Arnold [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 15, 2006 10:34 AM
To: Gump code and data
Subject: Junit nagging and CVS timeouts
Backstory: I've been on the junit mailing list for a few
hours trying
to track down a problem that has recently surfaced in the log4j unit
tests on Gump that I believe is due to a change in junit. To
complicate issues, the junit anonymous CVS server has been
unresponsive, so I haven't been able to see the code in question or
reproduce it the problem locally. So I've been driving blind with a
little help from Gump.
From your commit messages, I believe that it's the same Ant bug that was
killing commons-collections last week. The short version is that when
Ant
auto-detects JUnit-4, it doesn't look for the static suite() method, and
just assumes that you've defined all of your tests with Annotations.
Thanks, sounds like it. I'll pass it along to junit-devel. I couldn't
find a bugzilla issue related to it and it was hard to sort through all
the JUnit related threads on the Ant-dev mailing list.
Ant is still coming to terms with Junit4.
-There's just been a profound change in Ant's <junit> task which uses
reflection to load junit.jar, which means you dont need junit on Ant's
own classpath to use the task. We could, therefore, pull the
runtime="true" dependency on junit in ant's own descriptor, which would
break anyone who assumed that Ant came with junit.
-The junit4 support is new and stabilising; I think right now it looks
for junit3 on the classpath ahead of junit4 and goes for that first if
found, rolling back to junit4 otherwise.
-The Ant team is thinking of pulling all junit4 support out of <junit>
and into its own ant library, <junit4>, with its own test runner, XSL
transform, etc etc. <junit> is complex enough.
-Apparently the junit people want to set up a conf call with us, to
discuss <junit> futures. That call hasnt gone through yet so there is no
news. I think my #1 goal last week would have been to get them to care
about gump, but the big break is fixed there, and if the nag mail goes
to the group, they will have to care more. It may be that the remaining
change is to host the (proposed) junit4 task in the junit codebase. this
keeps the junit task+jar in perfect sync, though introduces a problem
for the junit task, namely being in sync with ant1.6 & 1.7.
-Steve
Well, David Saff agreed to be nagged personally (check the [EMAIL PROTECTED]
archives), not the entire junit project. There are a number of other
projects that nag an individual instead of the development list.
Since the
nags are usually once a day, it looks ok to change it to the junit-devel
list.
I had seen the message on [EMAIL PROTECTED], it was what alerted me to the
recent change in the descriptor. But I saw it after I started digging
into the apparent missed nag messages.
---------------------------------------------------------------------
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]
