Hide Forgot
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:
Assigning to Anthony to investigate.
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.
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).
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.