Open enebo opened 8 years ago
Ack I see the path forward and it is a little ugly. We need to override JavaPluginLoader.createRegisteredListeners in RubyPluginLoader. In this method if we can see it is a Ruby-derived class (not sure best way on this) we will set it up to use our own EventExecutor which generates a custom EventException which only returns the ruby bits of the backtrace. So not all that horrible...
In issue #56 we see a typical backtrace in Purugin as it stands today. Here is one I just generated:
You will see Java framework is generating a wrapped exception but the real exception we want is our RaiseException generated from the ruby runtime itself.
So the challenge is to overload the handler OR possibly subclass the PluginException itself to not show all the other crud of spigot/craftbukkit in getMessages (or whatever Java exception backtrace generating method is called).