Stephen, I guess the required classes of IP-finders should be in the classpath (libs directory). Currently, they are copied from the optional directory of the ignite binary package but would be copied from an appropriate ignite extension binary package. Probably I'm missing something but almost nothing changes in that process from my point of view. The documentation pages will be updated prior to the release.
On Wed, 13 Oct 2021 at 13:44, Stephen Darlington <stephen.darling...@gridgain.com> wrote: > > I understand the motivation from a development point of view, but how will > this work for end users? Currently, the documentation talks about extensions > only in terms of importing maven dependencies (download.cgi > <https://ignite.apache.org/download.cgi#extensions>). If I’m trying to start > a cluster on Azure, how does that work? Do I need to build my own server? > > Regards, > Stephen > > > On 13 Oct 2021, at 11:35, Nikita Amelchev <namelc...@apache.org> wrote: > > > > +1 to migrate and include to the Ignite 2.12 scope > > > > пн, 20 сент. 2021 г. в 17:09, Denis Magda <dma...@apache.org>: > >> > >> Perfect, thanks, Maxim! > >> > >> - > >> Denis > >> > >> > >> On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov <mmu...@apache.org> wrote: > >> > >>> Folks, > >>> > >>> > >>> I've created an issue [1] to move all cloud-based IP-finders to the > >>> ignite-extensions. The motivation is the same as with migration of > >>> Spring Data integration - to remove integration dependency of the > >>> release cycle on Ignite releases. > >>> > >>> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-15541 > >>> > > > > > > > > -- > > Best wishes, > > Amelchev Nikita > >
