New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drools 243 #243
Drools 243 #243
Conversation
Demian, could you please check and apply this fix to all the custom Evaluators? |
Yes! There are more. But I could only reproduce this issue with the CEP evaluators. As this This night I will do some more testing in the other operators and will let Thanks Davide! Demian On Tue, Aug 27, 2013 at 5:24 PM, Davide Sottara notifications@github.comwrote:
|
Hey Davide. I made another commits applying the same to other operators. I was trying to think how to make a test to reproduce it.. but I think it is not easy. One could be put a precompiled pkg in test classpath, and try to unmarshall it. But this will be not easy to maintain. Any idea? Thanks, Demian |
Demian, did you commit your second part of the fix? |
Sorry, apparently a browser glitch |
Did you forget to include the SetEvaluatorsDefinition? |
Bumps [junit](https://github.com/junit-team/junit4) from 4.12 to 4.13.1. - [Release notes](https://github.com/junit-team/junit4/releases) - [Changelog](https://github.com/junit-team/junit4/blob/main/doc/ReleaseNotes4.12.md) - [Commits](junit-team/junit4@r4.12...r4.13.1) --- updated-dependencies: - dependency-name: junit:junit dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
No description provided.