Bug 727562
Summary: | Missing Drools Flow | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Tomas Schlosser <tschloss> |
Component: | Build Process | Assignee: | Julian Coleman <jcoleman> |
Status: | VERIFIED --- | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | BRMS 5.2.0-ER1 | CC: | kverlaen, ldimaggi, mvecera, rzhang |
Target Milestone: | --- | ||
Target Release: | BRMS 5.2.0.GA | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
No release note content required as a this bug appears to be between internal builds only.
|
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: | |
Embargoed: |
Description
Tomas Schlosser
2011-08-02 13:13:45 UTC
*** Bug 728408 has been marked as a duplicate of this bug. *** hi, Tomas, does this issue remain in BRMS 5.2 ER2? As Kris suggested, jbpm-flow and jbpm-flow-builder jars have been included in BRMS 5.2 ER2. Yes, the Drools flow works with BRMS-5.2.0-ER2. However only DRF format is working. If we want to support BPMN2 format we would have to add more jBPM libraries (according to Len's comment it would be bpmn2). Note that it might bring the whole jBPM as transitive dependencies. (In reply to comment #4) > If we want to support BPMN2 format we would have to add more jBPM libraries > (according to Len's comment it would be bpmn2). Note that it might bring the > whole jBPM as transitive dependencies. Since we won't be bringing in BPMN2, I'm marking this as VERIFIED. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No release note content required as a this bug appears to be between internal builds only. |