Why wait? Seems really quite odd to have a current release stream with one of its noted features having been an upgrade to Spring 5, and a coming 5.17.1 release updating Spring to address the CVEs only fixed in Spring 5.x, still continuing having a deployed test module testing Spring 3. Not even remotely the latest version of Spring 3 either.
I think it should just be removed immediately, i.e before 5.17.1. On Thu, 31 Mar 2022 at 14:56, Matt Pavlovich <mattr...@gmail.com> wrote: > > Hi all- > > Is anyone aware of a use case or compelling reason to maintain the > activemq-itests-spring31? > > If not, I’ll plan to remove in 5.18.x. > > Thanks, > Matt Pavlovich
