Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: fuse-7.7-GA, fuse-7.8-GA
Affects Version/s: fuse-7.7-GA
Component/s: Tooling
Labels:
- POST_GA

Fuse Progress Bar:

% %
Target Release:

fuse-7.8-GA
Steps to Reproduce:

Hide

Follow the instructions in Chapter 2 of the Fuse 7.7 Getting Started guide:
https://access.redhat.com/documentation/en-us/red_hat_fuse/7.7/html-single/getting_started/index#getting-started-with-fuse-on-karaf

When you reach the end of Step 1. of Section 2.3 Building your first Fuse application on Karaf, you find that the the project fails to build.

Show
Follow the instructions in Chapter 2 of the Fuse 7.7 Getting Started guide: https://access.redhat.com/documentation/en-us/red_hat_fuse/7.7/html-single/getting_started/index#getting-started-with-fuse-on-karaf When you reach the end of Step 1. of Section 2.3 Building your first Fuse application on Karaf , you find that the the project fails to build.

SFDC Cases Counter:
SFDC Cases Links:

Description

Building the "Content Based Router - Blueprint DSL" example for Apache Karaf in CodeReady Studio fails, because the project references the wrong BOM version for Karaf. In particular, the quickstart POM contains these lines:

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.jboss.redhat-fuse</groupId>
        <artifactId>fuse-karaf-bom</artifactId>
        <version>7.8.0.fuse-sb2-780006</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>

Instead of referencing a Fuse 7.7 Karaf version, it's referencing a Fuse 7.8 Spring Boot 2 version.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

pom.xml
8 kB
2020/07/31 12:15 PM

Activity

People

Assignee:: Lars Heinemann

Reporter:: Fintan Bolton (Inactive)

Tester:: Dominik Jelínek

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2020/07/31 12:14 PM

Updated:: 2022/12/21 12:24 PM

Resolved:: 2020/09/17 6:43 PM