I have been discussing this with bob and seems we will probably have to
bite the bullet :( still this will not touch drools-core so should have
no effect on rule execution speed - only on ruleset loading/compiling.
Mark
peter royal wrote:
On Nov 8, 2005, at 10:06 AM, Mark Proctor wrote:
I have been hacking on commons jci as a standardised api for all our
compilers. However commons jci relies on commons logging. As Drools
grows and we rely on more third party resources we are going to
struggle to dissallow logging from module dependencies - in this case
it now effects drools-java, drools-groovy, drools-jsr and
drools-examples. I have discussed a ripped version of jci among other
alternatives. Looking to get feedback from other developers on this
issue.
*sigh* .. pressure torsten to fix JCI :)
-pete
--(peter.royal|osi)@pobox.com - http://fotap.org/~osi
