[jbosstools-issues] [JBoss JIRA] Created: (JBIDE-3670) Drools Runtime unclear how to correctly define

[Jeff DeLong (JIRA)]

Drools Runtime unclear how to correctly define
----------------------------------------------

                 Key: JBIDE-3670
                 URL: https://jira.jboss.org/jira/browse/JBIDE-3670
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: drools
    Affects Versions: 3.0.0.cr1
         Environment: jbdevstudio-linux-gtk-2.0.0.CR2-R200901250322.jar on RHEL 5, jdk 1.5.11
            Reporter: Jeff DeLong


I tested out the Drools IDE in JBDS. I used the Drools icon to create a new Drools project, and ran the DroolsTest class the wizard created as a Java Application. I got the following exception:

    java.lang.NoClassDefFoundError: org/antlr/runtime/CharStream

The problem is with defining the "Drools Runtime". As part of the setup for creating a Drools Project for the first time, the user is asked to create a "Drools Runtime". This is new (in the past Drools IDE new which set of jars to use), to be consistent with other tools and allow user to select different Drools Runtimes. The challenge for the user is how to define a Drools Runtime. You can either find the jars in JBDS plugins, explode them into a folder, and point to them, or download  Drools engine/expert (in this case I had decided to try jboss-brms-engine-5.ea.zip, since this is the .com version). However when this is unzipped, some jars are in the root of the folder and some are in a lib directory. At least four of the ones in the lib directory are required for runtime (antlr-runtime-3.1.1.jar, core-3.4.2.v_883_R34x.jar, mvel2-2.0.5.jar, xstream-1.3.1.jar), and the jars in a subdirectory are not added to the runtime classpath.

It should be easier for the user to define a Drools Runtime. They should not have to know about which jars to move around. They should just be able to download and unzip.
      



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira