Andi Vajda <va...@apache.org> wrote: > > At times like these it would be very handy to know just which class > > file > > is causing the problem. > > Indeed, I wish java would tell.
Yes, it's a very poorly designed exception. > All jcc can tell is what class it attempted to load not what class is > bad since loading a class can bring in a bunch more. > > I can add a catch to print out the attempted class name. That would help, thanks. I'm still a bit mystified as to how a bad version number could slip in there -- I'm using the same compiler for both JCC and GoodStuff. Bill
