James, On 10/20/05, James Carman <[EMAIL PROTECTED]> wrote: > Knut, > There are some failed assertions, too: > > http://vmgump.apache.org/gump/public/jakarta-hivemind/jakarta-hivemind-libra > ry/gump_work/build_jakarta-hivemind_jakarta-hivemind-library.html > > Of course, there's the on NullPointerException too. >
Yes, I see. I hadn't looked that closely at it. This Groovy really starts to annoy me. This is now the second time that they've broken the same feature! I first reported it sometime in february: http://jira.codehaus.org/browse/GROOVY-726. The problem occurs with the line precise error reporting test case. Since Groovy doesn't provide any other means I have to pull the line number out of an exception stack trace, which of course is quite ugly and expensive. But now it's the second time this line number is missing in the trace element of the Groovy script due to a change in Groovy. I'll "resolve" this issue the same way I did the last time. I'll just temporarily disable the line precise error reporting test case. --knut --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
