[CAMEL-14461] camel-core - Make RuntimeCatalog optional and in its own module

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 30/Jan/20 08:02
• Updated: 06/Feb/20 20:59
• Resolved: 06/Feb/20 20:59

Description

Lets see if we can move RuntimeCamelCatalog to its own module and make it optional.

Its used by component extension verifiers and components that use dynamic to optimization like toD with http components. But we can look at source code generate what they may need for this, so it can be more optional.

The new tooling model classes can then also become optional so we can keep plain Camel JARs to less JARs and classes.

Issue Links

• duplicates: CAMEL-14479 camel-core - Move RuntimeCamelContext to separate JAR