We had many issues using the upstream version of Camel JBang with the downstream Camel version, a productization of Camel JBang would solve all the issues, moreover, we can improve the developer experience for Red Hat customers.

In order to achieve full Camel JBang productization and ship it to customers the following has to be done

• Productize Camel JBang Core.
• Make sure that all the default Camel (SB and Q too) versions in camel-jbang-core are the productized and expected ones.
• Create an organization for Camel JBang https://github.com/redhat-camel/
• Create and maintain productized Camel JBang main class, ala https://github.com/Croway/jbang-catalog/
• Test it (it should be already possible, we modified the upstream test suite so that an external Camel JBang can be tested)
• Update documentation with jbang app install camel@redhat-camel

Dod:

• jbang app install camel@redhat-camel install the latest camel cli downstream version
• Given that camel-jbang-core is productized, and the camel versions are the downstream ones, I'd expect that camel can be used as is, we should not provide versions override anymore, but all the commands should work without overrides, and should use the expected, downstream version.