One problem with doing this in a static initializer is that you lose the
relevant exception. I would try moving this to a constructor or lazy-load
it, and you might get a better error message.
On Wed, Jun 5, 2013 at 1:28 PM, Jim - FooBar(); jimpil1...@gmail.comwrote:
Hello everyone,
On 05/06/13 18:40, Gary Trakhman wrote:
One problem with doing this in a static initializer is that you lose
the relevant exception. I would try moving this to a constructor or
lazy-load it, and you might get a better error message.
doing what you suggested seems to alleviate the problem!
The other alternative is to extend the class loader to add a trap.
I do not have the code handy but you might find it using a search on google.
Luc
One problem with doing this in a static initializer is that you lose the
relevant exception. I would try moving this to a constructor or
Jim - FooBar(); jimpil1...@gmail.com writes:
Now, the first time I (load-file xxx.core.clj) everything is
perfectly fine. The minute I make a change and re-load I get:
NoClassDefFoundError Could not initialize class yyy.Foo
This confuses me, because the JVM should only be loading and
