That sounds like a good plan to me. +1
On Mon, Jun 1, 2026 at 6:58 AM Claude Brisson via dev < [email protected]> wrote: > Another choice to do for the spring support... > > Since Spring 7 is out, having our new module named > spring6-velocity-support is rather cumbersome ; it does work with Spring > 6 or 7, so there shouldn't be any "6" in the name. > > My proposal: > > - rename the *old* module from spring-velocity-support to > spring5-velocity-support > > - rename the *new* module from spring6-velocity-support to > spring-velocity-support > > Strictly speaking, that would imply a major version jump since the new > "spring-velocity-support" is not backward compatible with the old > "spring-velocity-support". But this module being a marginal support > module, I think that this is acceptable if properly documented. > > +1/-1 ? > > On 07/05/2026 02.32, Claude Brisson via dev wrote: > >> Is there any code change required in Tools when going from Spring 5.x > >> to 6.x? > > > > The Tools counterpart for the Spring integration never saw the light > > for Spring 5.x since although I started it at the time, I never > > completed it, not being a Spring user myself. > > > > So, no, there is no impact on the tools. > > > > But with the help of AI, I can now propose a tools integration for > > Spring 6.x (basically mimicking what they do for Freemarker) in a new > > module, spring6-mvc-tools or alike. > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
