If you are referring to TomEE, the reason is quite simple. We have integration code for ActiveMQ Classic, but we don't seem to have any skills/knowledge on ActiveMQ Artemis to migrate our integration code.
I'm sure if someone would have the skills we would probably migrate. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, Feb 16, 2022 at 5:04 PM Justin Bertram <jbert...@apache.org> wrote: > I may be missing the point here, but why not use ActiveMQ Artemis' Jakarta > client implementation? It fully supports Jakarta Messaging 2.0 & 3.0. > > > Justin > > On Wed, Feb 16, 2022 at 9:15 AM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > Hi, > > > > I'd like to know if there is an available version of ActiveMQ Classic for > > Jakarta? > > I think we can have a quick approach with the shade plugin and I'm happy > to > > contribute it if it helps. > > > > Until we have to do deeper changes and logic, it may allow third party > > projects like TomEE to use it. > > > > WDYT? > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > >
