On Wed, 19 Aug 2009, Ludovico Cavedon wrote:
On Thu, Jun 18, 2009 at 7:49 PM, Andi Vajda<va...@apache.org> wrote:
Instead, I fixed half of bug PYLUCENE-1 [1] by including the stacktrace of a
Java exception into the string representation of the Python error object
wrapping it. When a JavaError is reported, the corresponding java stacktrace
is now included in the error message.
This is useful!
What about not aborting in case of findClass exception, but just
printing the the class name and the exception? (see attachment).
In HtmlUnit there are two classes that raise an exception, but I do
not care about them working (and the --exclude parameter has no effect
on findClass...)
Instead I changed the excludes set to no longer contain classes but their
names. A class listed with --exclude is no longer loaded unless it's a
dependency, of course. And in that case, skipping over the error is not an
option anyway.
This is committed in rev 806057.
Andi..
