By fixing bug https://bugzilla.redhat.com/show_bug.cgi?id=724753 (Drools should not allow two rules with same name in the same package) it was added new functionality that allows user to set which results created during building of package are considered as info, warning or error. Replacement of rule with the same name is not considered as error by default. But customer wanted this behaviour to be handled differently. Now he can choose it as warning or error. This new feature is not documented yet and it should be.
Done. [droolsjbpm-knowledge] etirelli pushed 1 new commit to 5.3.x: https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/ed8bf919c1479136011fe8b4e7b0782884225ef2 [drools] etirelli pushed 1 new commit to 5.3.x: https://github.com/droolsjbpm/drools/commit/ffc7025dc3c6e164d1678bbb743d036ea260c23a Commits were also cherry-picked into 5.4.x and master (5.5.x).
This fix has been committed to project branch which BRMS 5.3 used. So this requires to request block+ flag. It is javadoc issue which has code change in project.
Sorry. While writing the documentation I noticed that the compilation results did not have a default severity, so I added the default severity INFO into the code. I am requesting the blocker flag. I can rollback the change if necessary.
The fixed for this issue should be included in ER7. Please do verification on it.
As requested, I rolled back the code commit. The roll back commit is: https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/a5aa5bc4371225b7f0f9bf0bfe7b38955e700b48 For future reference, please note that without a default severity, compilation results that support user configured severity (e.g. rule updates) will generate a compilation result with a "null" severity, and such results will be "invisible" to all query methods by severity (e.g. getErrors()).
Moving to future as this won't be fixed in 5.3
Changed component to documentation so it doesn't get missed by documentation next release.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.