[Jelly] bug: JellyAssertionFailedError doesn't have script location

[Todd Jonker <tv...@pobox.com>]

The attached patch adds a test case for a bug that seems to have been
introduced recently.  In this case a JellyUnit JellyAssertionFailedError
doesn't have appropriate script location information.

Since this is my first attempt at adding Jelly test cases, please let me
know if I did something wrong!

Cheers,
.T.


-- 
To the mind that is still, the whole universe surrenders.
  -- Lao-Tzu, philosopher (6th century BCE)

Re: [Jelly] bug: JellyAssertionFailedError doesn't have scriptlocation

[James Strachan <ja...@yahoo.co.uk>]

From: "Todd Jonker" <tv...@pobox.com>
> The attached patch adds a test case for a bug that seems to have been
> introduced recently.  In this case a JellyUnit JellyAssertionFailedError
> doesn't have appropriate script location information.

Well spotted. The recent change to make JellyAssertionFailedError extend
from JUnit's AssertionFailedError had broken the error reporting code.

I've applied your unit test patch and fixed the bug. Great stuff


> Since this is my first attempt at adding Jelly test cases, please let me
> know if I did something wrong!

It was great.

You also seem to have found a new Jexl bug that ${ex.lineNumber != -1}
doesn't parse correctly for some reason. I've added this to the Jexl unit
tests as another failing unit test. For now as a work around I've used
${ex.lineNumber gt 0} in your JellyUnit test case.

James
-------
http://radio.weblogs.com/0112098/

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com