| Summary: | fuse-bxms-integration contain 2 versions of jboss-integration-platform-bom and unexpected dependencies change | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Ryan Zhang <rzhang> | ||||
| Component: | Fuse Integration | Assignee: | Aileen <aileenc> | ||||
| Status: | CLOSED EOL | QA Contact: | Lukáš Petrovický <lpetrovi> | ||||
| Severity: | urgent | Docs Contact: | Petr Penicka <ppenicka> | ||||
| Priority: | urgent | ||||||
| Version: | 6.3.0 | CC: | jcoleman | ||||
| Target Milestone: | CR1 | ||||||
| Target Release: | 6.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-03-27 20:04:50 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: | |||||
| Attachments: |
|
||||||
|
Description
Ryan Zhang
2016-04-28 04:24:28 UTC
[rzhang@/workspace/1fuse-bxms-integ]$grep "<version.org.jboss.integration-platform>6.0" -r * pom.xml: <version.org.jboss.integration-platform>6.0.6.Final</version.org.jboss.integration-platform> quickstarts/spring-camel-drools-decision-table/pom.xml: <version.org.jboss.integration-platform>6.0.0.Final</version.org.jboss.integration-platform> quickstarts/blueprint-camel-drools-decision-table/pom.xml: <version.org.jboss.integration-platform>6.0.0.Final</version.org.jboss.integration-platform> quickstarts/jbpm-workitems-camel/pom.xml: <version.org.jboss.integration-platform>6.0.0.Final</version.org.jboss.integration-platform> Created attachment 1151737 [details]
fbi-patch.text
1) jboss-integration-platform-bom version should be the same (ie 6.0.6.Final in this case I agree with you. But this is just going to affect in the quickstart execution. As the quickstart is independent (not extending from a parent pom), I do not see this as a blocker. 2)quickstart shouldn't report camel dependencies not defined error. But in this case, I think the camel version has been removed from the bom. From which bom is it expected to read camel dependencies? 3)is that possible to keep 8.1.14 for jetty if there is no blocker reason to upgrade the 3rd parties dependencies since we are very close to GA This was upgraded, because it was a compilation error after the upgrade to fuse 6.3. So I do not think this is possible. (In reply to David Virgil from comment #6) > 3)is that possible to keep 8.1.14 for jetty if there is no blocker reason to > upgrade the 3rd parties dependencies since we are very close to GA > This was upgraded, because it was a compilation error after the upgrade to > fuse 6.3. So I do not think this is possible. I realise that I was building without the fuse-6.2.1 profile when I saw the jetty update. We do keep jetty 8.1.14 with the fuse-6.2.1 profile, so this is not a problem when we build with the profile. Yes Julian, we keep jetty 8.1.14 with the fuse 6.2.1 profile. (In reply to David Virgil from comment #6) > 1) jboss-integration-platform-bom version should be the same (ie 6.0.6.Final > in this case > > I agree with you. But this is just going to affect in the quickstart > execution. As the quickstart is independent (not extending from a parent > pom), I do not see this as a blocker. It means that the quickstarts haven't been tested with the newer product BOM, and that means that we see: > 2)quickstart shouldn't report camel dependencies not defined error. > > But in this case, I think the camel version has been removed from the bom. > From which bom is it expected to read camel dependencies? when we use the same BOM for the quickstarts as we use in the rest of the project (6.0.6). Using 2 different BOM versions seems very odd, especially as the specific change to the BOM is to fix a problem related to camel version mismatches. If the quickstarts use the earlier BOM, then won't building projects using camel but based on the quickstarts as examples run into problems? If so, then this is another reason to update the BOM that the quickstarts use. Hi Julian, The jboss-integration-platform-bom only appears in 3 quickstarts: jbpm-workitems-camel blueprint-camel-drools-decision-table spring-camel-drools-decision-table (In reply to David Virgil from comment #6) > 1) jboss-integration-platform-bom version should be the same (ie 6.0.6.Final > in this case > > I agree with you. But this is just going to affect in the quickstart > execution. As the quickstart is independent (not extending from a parent > pom), I do not see this as a blocker. Yes, it only affect the 3 quickstarts you mentioned. Those quickstart are included in the deliverables and they are in the path of build the project. Shouldn't we fix this or should we remove the quickstarts? > 2)quickstart shouldn't report camel dependencies not defined error. > > But in this case, I think the camel version has been removed from the bom. > From which bom is it expected to read camel dependencies? I *think* it should probably read from the top pom.xml or fuse parent bom. If quickstart shouldn't have a parent, would it make sense to import the pom? (please correct me if it doesn't make sense to you) > 3)is that possible to keep 8.1.14 for jetty if there is no blocker reason to > upgrade the 3rd parties dependencies since we are very close to GA > This was upgraded, because it was a compilation error after the upgrade to > fuse 6.3. So I do not think this is possible. Should we use the profile in this case? And I noticed that the versio.fuse in default said 6.2.1.redhat-084. My original understanding is there is no need to build from profile since there are two separte tags for each comibnations. And the properties in default are defined for Fuse 6.2.1 combinations. (In reply to David Virgil from comment #10) > The jboss-integration-platform-bom only appears in 3 quickstarts: > > jbpm-workitems-camel > blueprint-camel-drools-decision-table > spring-camel-drools-decision-table Indeed. However, for consistency, I think that we should be using BOM 6.0.6, as that is the version we're using for the product. The quickstarts should be able to be used as a template for further work. With the current code, if I extend one of these quickstarts and add further camel dependencies, then I'm likely to hit problems with version mismatches (which caused the removal of camel artifacts in 6.0.6). If I need to use BOM 6.0.6 to use camel dependencies, then that should also be reflected in the quickstarts, otherwise they are not good as templates for extending. |