Our Eclipse tooling hasn’t received much love over the years, and no one from community has ever stepped up :(
We might have some one internal to RHT that might be able to help in the near future, but that will take a few weeks before I hear anything. We in the Drools team tend to stick with plain text editors and logging :) Mark On 27 May 2014, at 10:48, Péter Gergely, Horváth <h.pe...@mailbox.hu> wrote: > Hi All, > > I am evaluating Drools 6 for one of our projects but found a strange issue > with Eclipse integration; debug functionality does not seem to work at all. > Only Rules view displays the rules (which is I believe independent from the > debugger) but all of the other views (Agenda, Audit, Global Data, Process > Instance, Process Instances, Working Memory) are always empty. > > I have confirmed that Drools nature is enabled on the project (it is actually > the example project generated by the Eclipse plugin) and I start my class as > a Drools application in Debug mode. (It is the com.sample.DroolsTest from the > plugin-generated sample project) > > My Eclipse environment is the following: > > Drools plugin installed: > JBoss Drools Core 6.0.0.Final > JBoss Drools Guvnor 6.0.0.Final > JBoss jBPM Core 6.0.0.Final > > Eclipse release information: > Spring Tool Suite > Version: 3.5.1.RELEASE > Build Id: 201405030657 > Platform: Eclipse Juno SR2 (3.8.2) > > Version of Drools Runtime is 6.0.1 Final > > > Does anyone have any idea what could be wrong? For me one of the most > powerful features of Drools seemed to be its Eclipse-based rule debugging > capability. Could someone please help fixing my Eclipse Drools setup? > > Thanks, > Peter > > > _______________________________________________ > rules-users mailing list > rules-users@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
