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.
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]
