search

fabric8io / fabric8

fabric8 is an open source microservices platform based on Docker, Kubernetes and Jenkins
http://fabric8.io/
1.76k stars 504 forks source link

Remove camel dependency in fabric8 pom #6434

Open davsclaus opened 8 years ago

davsclaus commented 8 years ago

We dont have any camel components in fabric8 and we should IMHO remove Camel as it allows other projects to be more free.

For example the quickstarts import fabric8 which they don't really need but should import that f-m-p and then they should all specify what version of Camel they use. So they are all standalone.

This also allows us to specify Camel version more freely in fabric8-forge / django and other projects, that otherwise would get locked into fabric8 bom.

nicolaferraro commented 8 years ago

Claus, I used the fabric8 bom in some spring Boot quickstarts because the amount of boms that should have been included there was growing, and we are going to productize them shortly as part of FIS 2.0. Indeed the "microservice suite" of dependencies required in such quickstarts include the kubernetes model and client from fabric8, as well as the testing related stuff, the spring boot BOM, the new camel dependencies BOM and all the new additions in spring-cloud-kubernetes (to be added after next release). That's why we opted for a unique "fabric8+spring-boot+camel" BOM instead of 4 BOMs per quickstart. It was a product requirement but it made sense to do it upstream for these reasons. Do you need to set the camel version in some specific quickstart?