Bug 1018811
Summary: | Use Community BOM for Riftsaw | ||
---|---|---|---|
Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Nick Cross <ncross> |
Component: | BPEL Integration | Assignee: | Gary Brown <gbrown> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Sedlacek <jsedlace> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.0 GA | CC: | atangrin, ldimaggi, oskutka, soa-p-jira |
Target Milestone: | ER7 | ||
Target Release: | 6.0.0 | ||
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: | |
Embargoed: |
Description
Nick Cross
2013-10-14 12:55:52 UTC
Have moved bpaf-explorer, riftsaw-ode and riftsaw repos over to use the community bom. However when trying bpm-console, just adding the jboss-as-parent and importing the integration bom, caused the GWT compilation phase to blow up without any helpful information. As the bpm-console uses (depends upon) old versions of GWT and Errai, these would not be aligned with the bom anyway. The console will also be re-written for 6.1 aswell. So after discussion with Nick, we have agreed that we bpm-console will not use the community bom. Gary Brown <gary> updated the status of jira RIFTSAW-543 to Resolved verified in ER7 |