Bug 1018811 - Use Community BOM for Riftsaw
Summary: Use Community BOM for Riftsaw
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: BPEL Integration
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER7
: 6.0.0
Assignee: Gary Brown
QA Contact: Jiri Sedlacek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-14 12:55 UTC by Nick Cross
Modified: 2015-08-02 23:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RIFTSAW-543 0 Major Resolved Move to community integration BOM 2013-12-18 13:37:55 UTC

Description Nick Cross 2013-10-14 12:55:52 UTC 
Riftsaw should import dependencies from the community bom (https://github.com/jboss-integration/jboss-integration-platform-bom/)
Comment 2 Gary Brown 2013-11-06 15:56:06 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.
Comment 3 JBoss JIRA Server 2013-11-06 16:04:34 UTC 
Gary Brown <gary> updated the status of jira RIFTSAW-543 to Resolved
Comment 4 Jiri Sedlacek 2013-12-18 13:37:44 UTC 
verified in ER7
Note You need to log in before you can comment on or make changes to this bug.