wood burning stoves 2.0
The moose likes IDEs, Version Control and other tools and the fly likes JUnit, Eclipse, and Drools Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "JUnit, Eclipse, and Drools" Watch "JUnit, Eclipse, and Drools" New topic

JUnit, Eclipse, and Drools

Mike Dean

Joined: Sep 28, 2005
Posts: 14
I have a plugin that contains core Drools jars and their dependencies. When I use the plugin in my RCP, it functions flawlessly. The RCP works, etc.

When I try to unit test, however, something is foul about classloading or something. Whether I add the plugin to the classpath of the unit test configuration in Eclipse, or stick everything in my Java home extensions, etc., I get an error. Here is the test setup code:

Note that this code is nearly identical to the code I use in my RCP, and it works there. However, when I try to run the code as a unit test:

I have gone into the source of Drools, and cannot find any hint of what is wrong here. But the question I think revolves around how Eclipse handles the classpath of unit tests, compared to how classpaths are handled when applications are compiled into RCP standalones.

Thanks in advance. This has stumped me now for about 3 weeks.

- Mike
I agree. Here's the link: http://aspose.com/file-tools
subject: JUnit, Eclipse, and Drools
It's not a secret anymore!