... so I upgraded us to a patched 3.12.0.GA of javassist and that
cured all sorts of woes with our local Google AppEngine development
appserver and tapestry...
... until I tried to run code-coverage stats. Apparently our code-
coverage system at Google conflicts somehow with what javassist is
doing, and I get test failure when running instrumented code, but it's
fine when running uninstrumented code. <sigh>
This isn't a show-stopper, but it's damned annoying. Anyway, the
sooner Javassist can be ripped out, the better, in my opinion.
cheers,
Christian.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
