Hi Clebert We know but these point here was more a discussion to the community if it makes sense to remove the component in 5.16.x.
And actually it’s something we discussed in the original PR (I forgot): we agreed to remove on for coming 5.17.x releases. Regards JB > Le 14 janv. 2022 à 23:17, Clebert Suconic <clebert.suco...@gmail.com> a écrit > : > > you guys should use cherry-pick -x between main and 5.16.x > > > then you could use this type of reporting I'm generating for between > main and 2.19.x on activemq artemis. it's fairly helpful I think. > easier to manage what's missing between the branches... > > > let me know if you need some help using that..(although I'm not > available next week as I'm going out on a trip for a family issue) > >> On Wed, Jan 12, 2022 at 10:22 AM JB Onofré <j...@nanthrax.net> wrote: >> >> Ok I remember the discussion now. >> >> Let’s keep it in 5.16.x and focus on 5.17.0 where it’s already removed. >> >> Sorry about the noise ;) >> >> Regards >> JB >> >>>> Le 12 janv. 2022 à 16:06, Jean-Baptiste Onofre <j...@nanthrax.net> a écrit >>>> : >>> >>> Yes, I know: my point is also to remove from activemq-5.16.x >>> >>> If no objection, I will remove it from there. >>> >>> Thanks, >>> Regards >>> JB >>> >>>> Le 12 janv. 2022 à 16:03, Matt Pavlovich <mattr...@gmail.com> a écrit : >>>> >>>> Hey JB- >>>> >>>> I already removed it from 5.17.0 (main) >>>> >>>> -Matt >>>> >>>>>> On Jan 12, 2022, at 4:16 AM, Jean-Baptiste Onofré <j...@nanthrax.net> >>>>>> wrote: >>>>> >>>>> Hi all, >>>>> >>>>> ActiveMQ provides activemq-camel component. >>>>> >>>>> This component is "old" (using Camel 2.25.x) and has been replaced by >>>>> camel-activemq and/or camel-jms. >>>>> >>>>> I propose to remove ActiveMQ Camel from the ActiveMQ code. >>>>> >>>>> Thoughts ? >>>>> >>>>> Regards >>>>> JB >>>> >>> >> > > > -- > Clebert Suconic
