From: rules-dev-bounces@lists.jboss.org [mailto:rules-dev-bounces@lists.jboss.org] On Behalf Of Wolfgang Laun
Sent: 19 September 2011 17:15
To: Rules Dev List
Subject: Re: [rules-dev] Formal verification of Drools - master's thesis

On 19 September 2011 17:57, Mauricio Salatino <salaboy@gmail.com> wrote:

Hi Jiri,

Drools Verifier do that for you? Am I right?

I think this is a misunderstanding. Looking at Drools' Java code takes a Java bug finding program such as findbugs. What Drools Verifier does is: look at DRL code written by Drools users.

Findbugs applied to Drools code is a good idea, but I would opt for this to include fundamental code that's used by Drools and responsible for a considerable number of JIRAs.

[Swindells, Thomas] I’d agree, but I think this ideally would include the bytecode output by drools – not the user specific parts (if users put issues in their code it’s their own fault) but the boiler plate code it produces.

-W

Toni Rikkola is the man behind drools verifier, you can talk with him to improve what he has now. I know that Esteban was also playing with that and adding the concept of Working Set. You can talk with him as well.

Cheers

On Mon, Sep 19, 2011 at 12:43 PM, Ansgar Konermann <ansgar.konermann@googlemail.com> wrote:

If I'm eligible to vote, please go for option 1.

Am 19.09.2011 17:14 schrieb "Jiri Svitak" <jsvitak@redhat.com>:

_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

--
- CTO @ http://www.plugtree.com
- MyJourney @ http://salaboy.wordpress.com

- Co-Founder @ http://www.jugargentina.org
- Co-Founder @ http://www.jbug.com.ar

- Salatino "Salaboy" Mauricio -

_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev