Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
False
-
%
-
Todo
Description
We're trying to exclude modules in camel using Guillaume's maven-exclude extension to cut down on the number of CVE that camel is hit with. The camel-catalog is causing issues in that it requires json from all components in the source tree, whether or not they have been module-excluded or not.
- is the camel-catalog necessary to build? Can we exclude it? Luca is working on changes to camel-k-runtime to replace the use of the camel-catalog there with - are there dependencies on camel-catalog in other projects? It looks like it is used in camel-quarkus in the generation of the camel-quarkus catalog, I am not sure what other dependencies on the camel-catalog there are in camel or other projects
- can we build a camel-catalog that only includes the components built?
- is a partial camel-catalog a possibility? In camel-quarkus we are providing community versions in descriptors / boms for versions we are not building in the productized build. I don't see any versions in the json files though, so I'm not sure a camel-catalog with community and productized versions is possible without changes
- should we be shipping a camel-catalog that includes components that we aren't really producing?