Details
-
Feature Request
-
Resolution: Obsolete
-
Major
-
None
-
7.3.1
Description
Today the projects generated using the Fuse Tooling wizard and Camel archetypes do not use
the jboss-fuse-parent BOM.
Instead the generated pom.xml use a static version for the camel artifacts.
<dependencies> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-core</artifactId> <version>2.15.1.redhat-620133</version> </dependency> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-blueprint</artifactId> <version>2.15.1.redhat-620133</version> </dependency> ... <dependencies>
To avoid the use of wrong/or incompatible camel artifact versions would be nice to use the Fuse parent BOM instead.
... <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding> <jboss.fuse.bom.version>6.2.0.redhat-133</jboss.fuse.bom.version> </properties> ... <dependencyManagement> <dependencies> <dependency> <groupId>org.jboss.fuse.bom</groupId> <artifactId>jboss-fuse-parent</artifactId> <version>${jboss.fuse.bom.version}</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> ... <dependencies> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-core</artifactId> </dependency> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-blueprint</artifactId> </dependency> ... <dependencies>
Thus the user don't have to worry about the correct/or compatible versions of the camel artifacts. And avoid issues when deploying the project to the Fuse Fabric environment.