Glad that I could actually contribute something back to this great project.
I put together a patch for this issue in the JIRA at
http://jira.jboss.org/jira/browse/JBRULES-1618 as promised.
Best regards
Marcus
On Tue, May 20, 2008 at 2:34 AM, Mike Dean [EMAIL PROTECTED] wrote:
Sorry to ask
Marcus, can you please open a JIRA for us, anyway, so that we can improve
that code spot to check for nulls? This will avoid such problems in the
future.
If you want to contribute a patch, it is also welcome.
Thanks.
Edson
2008/5/19 Marcus Ilgner [EMAIL PROTECTED]:
Hi Edson,
Sorry to ask question and then figure it out! I just substituted the actual
name of my suite class instead of saying this.class and it works
beautifully. I am now testing Drools with JUnit 4 with no problems, after
nearly six months! THANK YOU.
- Mike
Mike Dean wrote:
Thanks to both of
Thanks (months later!). I have cut down my code example below to show this
issue more clearly:
John J. Franey wrote:
NullPointerException on line 146 means classLoader is null. That is odd.
I have no idea why the code that gets classLoader won't work in eclipse's
junit runtime, but
Mike,
This looks like a classpath problem indeed. Did you tried asking the JVM
to dump its classpath so that you can know for sure what jars are included
and if any of them embeds a non-compatible ASM version ?
[]s
Edson
2007/12/30, J Michael Dean [EMAIL PROTECTED]:
Continuing to
NullPointerException on line 146 means classLoader is null. That is odd. I
have no idea why the code that gets classLoader won't work in eclipse's
junit runtime, but does when run in your eclipse plugin.
I'm not a plugin developer but I have a hunch that the junit environment for
plugin
