Re: Move Spring Data modules into Ignite extension project
Hello! Since Spring Data integration is actively used (compared to most others), I would argue that it should only moved to extensions last, when this process is debugged thoroughly and when we have at least one "essentials + extensions" release shipped with feedback. I think such release would be 2.9, so I think we should only move Spring Data to extensions after 2.9 is released and feedback from this release processed. Regards, -- Ilya Kasnacheev пн, 3 февр. 2020 г. в 10:39, Sergey Chernolyas : > Hi igniters! > > I would ask the community to allow for moving Spring Data modules to > project Ignite extensions. The base reason for it is Spring Data modules > aren’t Ignite modules. They are modules which allow using Ignite more > simpler and corresponds to Spring Framework. I mean that the modules isn’t > included to Ignite core, they are implementation of Spring Data interface. > I think it is more logical to move the modules to extension project. Plus, > Ignite (and its core modules) has long development cycle (about 6 months). > It is an additional reason to move modules with short development cycle to > extension project. > > May we do it? When (which release for?) and how? > > - > > With best regards, Sergey Chernolyas >
Re: Move Spring Data modules into Ignite extension project
Hi, I agree with you. I'm going to add some extra features to it too. I suppose we are able to use Nikolay Izhikov's experience with the spring boot starter. But we should remove it from Ignite after release this module. пн, 3 февр. 2020 г. в 10:39, Sergey Chernolyas : > Hi igniters! > > I would ask the community to allow for moving Spring Data modules to > project Ignite extensions. The base reason for it is Spring Data modules > aren’t Ignite modules. They are modules which allow using Ignite more > simpler and corresponds to Spring Framework. I mean that the modules isn’t > included to Ignite core, they are implementation of Spring Data interface. > I think it is more logical to move the modules to extension project. Plus, > Ignite (and its core modules) has long development cycle (about 6 months). > It is an additional reason to move modules with short development cycle to > extension project. > > May we do it? When (which release for?) and how? > > - > > With best regards, Sergey Chernolyas >
Move Spring Data modules into Ignite extension project
Hi igniters! I would ask the community to allow for moving Spring Data modules to project Ignite extensions. The base reason for it is Spring Data modules aren’t Ignite modules. They are modules which allow using Ignite more simpler and corresponds to Spring Framework. I mean that the modules isn’t included to Ignite core, they are implementation of Spring Data interface. I think it is more logical to move the modules to extension project. Plus, Ignite (and its core modules) has long development cycle (about 6 months). It is an additional reason to move modules with short development cycle to extension project. May we do it? When (which release for?) and how? - With best regards, Sergey Chernolyas
