Hi, Maksim. First of all, thanks for your efforts.
I have one concern, and probably I'm over exaggerating this problem, but which Spring version we're targeting? Spring 6? What we're going to do if, let's say after couple of years, Spring 7 will appear <https://spring.io/blog/2024/10/01/from-spring-framework-6-2-to-7-0> that won't be totally compatible with Spring 6?
So what I'm trying to highlight is should we try to use more sophisticated approach for Spring extension module naming? I.e. instead of *ignite-autoconfigure:3.0.0* we can have *ignite-spring6-autoconfigure:3.0.0*. In case of new Spring 7 we could simply spawn a new dedicated module for S7 and there would be no uncertainty for end user that he need to pick.
On 22.11.2024 13:35, Maksim Myskov wrote:
Hello Ignite devs, Please, take a look at the proposal for Ignite3 https://cwiki.apache.org/confluence/display/IGNITE/IEP-130%3A+Spring+Boot+support -- Maksim Myskov
