Future of ActiveMQ 5.x with nearing EOL of Spring 5.3.x

["Boeltl, Stefan" <St...@fisglobal.com.INVALID>]

Dear ActiveMQ committers,

Looking at https://spring.io/projects/spring-framework#support I see with worries that Spring 5.3.x EOL is around the corner (end of OSS support: 2024-08-31) and knowing that ActiveMQ 5.x is using / depending on Spring 5.3.x, I really would love to hear, what the plans for the time after 2024-08-31 will be.
(Worst case scenario: no more support / security updates for 5.x versions of ActiveMQ - better to know this asap!)

Thanks!

Kind regards
Stefan
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. Message Encrypted via TLS connection

Re: Future of ActiveMQ 5.x with nearing EOL of Spring 5.3.x

[Matt Pavlovich <ma...@gmail.com>]

Hello Stefan-

ActiveMQ 6.x was released last fall and supports JDK 17, Spring 6 and Jakarta EE messaging. This the moving forward target release for ActiveMQ 5.x users to avoid the Spring 5 deprecation.

ActiveMQ 6.x downloads: https://activemq.apache.org/components/classic/download/

ActiveMQ 5.x will stay on Spring 5.

This is all community support, so it is best effort. If you need formalized support, checkout the commercial offerings: https://activemq.apache.org/support

Thanks,
Matt Pavlovich

> On Mar 25, 2024, at 10:45 AM, Boeltl, Stefan <St...@fisglobal.com.INVALID> wrote:
> 
> Dear ActiveMQ committers,
> 
> Looking at https://spring.io/projects/spring-framework#support I see with worries that Spring 5.3.x EOL is around the corner (end of OSS support: 2024-08-31) and knowing that ActiveMQ 5.x is using / depending on Spring 5.3.x, I really would love to hear, what the plans for the time after 2024-08-31 will be.
> (Worst case scenario: no more support / security updates for 5.x versions of ActiveMQ - better to know this asap!)
> 
> Thanks!
> 
> Kind regards
> Stefan
> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. Message Encrypted via TLS connection

Re: Future of ActiveMQ 5.x with nearing EOL of Spring 5.3.x

[Jean-Baptiste Onofré <jb...@nanthrax.net>]

Hi Stefan

ActiveMQ 6.x is using Spring 6.x. As ActiveMQ 5.x will be "not active"
soon, I think it's ok and encourage users to upgrade to ActiveMQ 6.x.

NB: For ActiveMQ 7.x, I'm working on a PoC to remove Spring dependency
and use pure SPI/Loader.

Regards
JB

On Mon, Mar 25, 2024 at 4:45 PM Boeltl, Stefan
<St...@fisglobal.com.invalid> wrote:
>
> Dear ActiveMQ committers,
>
> Looking at https://spring.io/projects/spring-framework#support I see with worries that Spring 5.3.x EOL is around the corner (end of OSS support: 2024-08-31) and knowing that ActiveMQ 5.x is using / depending on Spring 5.3.x, I really would love to hear, what the plans for the time after 2024-08-31 will be.
> (Worst case scenario: no more support / security updates for 5.x versions of ActiveMQ - better to know this asap!)
>
> Thanks!
>
> Kind regards
> Stefan
> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. Message Encrypted via TLS connection