Re: [rules-dev] ClassFieldInspector and Groovy Classes

2007-04-16 Thread Edson Tirelli
Terry, A bad commit from my part. It shall work now. Regards, Edson 2007/4/16, Terry Laurenzo <[EMAIL PROTECTED]>: The following issue (737) was marked as closed, but in the current SVN the affected code is commented out -- once again rendering Groovy fact classes inoperable. Can

Re: [rules-dev] ClassFieldInspector and Groovy Classes

2007-04-16 Thread Terry Laurenzo
The following issue (737) was marked as closed, but in the current SVN the affected code is commented out -- once again rendering Groovy fact classes inoperable. Can anyone explain why the patch was backed out? If not, could we reopen JBRULES-737 as a regression or uncomment the check for

Re: [rules-dev] ClassFieldInspector and Groovy Classes

2007-03-14 Thread Edson Tirelli
Terry, Thank you for reporting and providing the patch. Patch applied: http://jira.jboss.com/jira/browse/JBRULES-737 []s Edson Terry Laurenzo wrote: The attached diff (against 3.0.5 sources) adds a condition to the ClassFieldInspector to not analyze methods named . For some

[rules-dev] ClassFieldInspector and Groovy Classes

2007-03-14 Thread Terry Laurenzo
The attached diff (against 3.0.5 sources) adds a condition to the ClassFieldInspector to not analyze methods named . For some reason, the Groovy compiler is outputing classes that were causing this check to choke and throw an IllegalArgumentException because of a method with ACC_PUBLIC ac