Great. JIRA created for the guide, I’ll get on that next week. ref: https://issues.apache.org/jira/browse/AMQ-8271
> On May 21, 2021, at 9:48 AM, Jean-Baptiste Onofre <j...@nanthrax.net> wrote: > > Hi Matt, > > It sounds like a plan. > > IMHO, (1) is the most important (on both 5.17/5.16). > > (2) can be targeted to 5.17.x for sure. > > Regards > JB > >> Le 21 mai 2021 à 15:49, Matt Pavlovich <mattr...@gmail.com> a écrit : >> >> JB- >> >> Agreed that we can start to wind down activemq-camel. >> >> How about: >> >> 1. Remove activemq-camel from activemq-osgi >> 2. Keep activemq-camel as a module in the build >> 3. Create a ticket for ‘Guide to ActiveMQ 5.1+ Camel 3.x' >> >> There are a *ton* of Camel examples online that reference the >> ActiveMQComponent (and its package naming) that is different from the >> camel-activemq module >> >>> On May 21, 2021, at 4:09 AM, Jean-Baptiste Onofre <j...@nanthrax.net> wrote: >>> >>> Hi everyone, >>> >>> In the process to upgrade and cleanup Apache ActiveMQ, I would like to >>> propose to remove activemq-camel component from Apache ActiveMQ. >>> >>> Since Camel 3.x, Camel provides camel-activemq component (with the >>> corresponding Apache Karaf feature), and also, >>> camel-jms/camel-amqp/camel-mqtt work fine with ActiveMQ. >>> So, I think that activemq-camel component is not useless, and it’s still >>> using camel 2.x. >>> >>> My proposal is to remove activemq-camel and cleanup the headers in >>> activemq-osgi. >>> >>> Thoughts ? >>> >>> Regards >>> JB >> >
