Bug 1322438

Summary: Inconsistent versions of Camel in integration package and BxMS product BOM (build 1.4.0-redhat-001)
Product: [Retired] JBoss BRMS Platform 6 Reporter: Jiri Petrlik <jpetrlik>
Component: Build and AssemblyAssignee: Ryan Zhang <rzhang>
Status: CLOSED EOL QA Contact: Jiri Petrlik <jpetrlik>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.3.0CC: kverlaen, rrajasek, rzhang
Target Milestone: ER3   
Target Release: 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
build 1.4.0-redhat-001
Last Closed: 2020-03-27 20:12:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1264565    

Description Jiri Petrlik 2016-03-30 13:53:05 UTC
Description of problem:

Using of integration package bom "fuse-integration-bom" together with our product bom "jboss-brms-bpmsuite-platform-bom" leads to use of wrong version of Camel (2.16.2). This integration package (build 1.4.0-redhat-001) is aligned with Fuse 6.2.1, which uses Camel version 2.15.1.

If our customers use "fuse-integration-bom" together with "jboss-brms-bpmsuite-platform-bom", they will compile applications against newer version of Camel than is supported in Fuse 6.2.1.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Rajesh Rajasekaran 2016-03-31 19:15:42 UTC
Assigning to Anthony to investigate.

Comment 3 Ant Stephenson 2016-04-04 12:45:15 UTC
Re-assigning to Petr as he already begun investigating. There are on-going discussions via e-mail on the best approach to solve this issue, nothing to report yet.

Comment 4 Petr Široký 2016-04-05 14:41:45 UTC
From my point of view, the best solution would be to remove the Camel dependencies from ip-bom (https://github.com/jboss-integration/jboss-integration-platform-bom/blob/6.0.x/ip-bom/pom.xml#L701) and let users choose the version they want (e.g. the one that is supported on the Fuse version they use).

Comment 5 Edson Tirelli 2016-04-06 20:55:07 UTC
As discussed by e-mail and agreed with the Fuse team, the camel dependencies were removed from the IP BOM:

https://github.com/jboss-integration/jboss-integration-platform-bom/pull/298

https://github.com/jboss-integration/jboss-integration-platform-bom/commit/9458fb75fe941e6ab1d9318b25eb748ee37e7a04

This will be included in the 6.3.0.ER3 build.