Bug 788582

Summary:	Write documentation for getting build results from KnowledgeBuilder by their severity
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Jiri Svitak <jsvitak>
Component:	Documentation	Assignee:	brms-docs <brms-docs>
Status:	MODIFIED ---	QA Contact:	Lukáš Petrovický <lpetrovi>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	BRMS 5.3.0.GA	CC:	atangrin, lpetrovi, mbaluch, rzhang
Target Milestone:	---	Keywords:	Documentation
Target Release:	future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jiri Svitak 2012-02-08 14:15:43 UTC

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.

Comment 3 Edson Tirelli 2012-04-27 17:35:37 UTC

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).

Comment 4 Ryan Zhang 2012-05-11 11:31:51 UTC

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.

Comment 5 Edson Tirelli 2012-05-11 16:26:43 UTC

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.

Comment 6 Ryan Zhang 2012-05-14 08:17:10 UTC

The fixed for this issue should be included in ER7. Please do verification on it.

Comment 7 Edson Tirelli 2012-05-14 14:17:49 UTC

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()).

Comment 8 Lukáš Petrovický 2012-05-14 14:40:59 UTC

Moving to future as this won't be fixed in 5.3

Comment 9 lcarlon 2012-06-18 04:12:46 UTC

Changed component to documentation so it doesn't get missed by documentation next release.