Conor MacNeill wrote: > > There seems to be a problem building junit fully at the moment (testing > it actually). > > http://jakarta.apache.org/builds/gump/latest/junit.html > > It's a silent failure because the junit build file does not use the > failonerror attribute when running its test with <java>. Anyway, I think > the problem is actually in gump. When I run gump locally, it seems to > generate a strange value for the dist property > > I'm still getting up to speed on Gump and I haven't tracked down the > cause yet. I'm off to bed right now so I thought someone else may be > able to track it down.
It's been that way nearly forever. When I last looked at it, the problem was that the javac task didn't put the classes into a separate directory so that the generated classes are in the current directory. This affects means that they are picked up in the test that tries to verify classloader semantics which complains. I tried to contact the owners of junit, but never got a response. More recently, a new developer on the junit team did comment on this, but I didn't follow up sufficiently to provide details. - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
