Various rules stop firing when they are in unlucky packagename and there is a function declared and also a type declared

A certain rule suddenly stops firing when adding more and more rules to the knowledge base, which (not only?) on first sight have nothing to do with the rule in question.

We created a few unit tests which show the faulty behaviour.

What we observed so far:

• when using declared functions plus declared data types, this error occurrs.
• sometimes, one can work around this problem by renaming a package. We're not sure if this is a reliable workaround, i. e. works in all situations.
• one can work around this problem by not using declared functions. We're not sure if this is a reliable workaround.

Find attached a ZIPed git repository containing:

• a Maven 2.1+ pom.xml suitable to trigger the unit tests via mvn test
• Java source files for a TestNG-based unit test
• example drools source files to illustrate the problem (used by the unit tests)

Please have a look at java file RuleDoesNotFireIfUsingDeclaredFunctionAndTooManyPackages.java. This should make quite clear what we're expecting of the drools library and where it fails to fulfil these expectations.