You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Maxim Muzafarov <mm...@apache.org> on 2022/04/26 13:24:23 UTC
[DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions
Hello Igniters,
Currently we have a batch of ignite-hibernate modules which provide
Hibernate second-level cache (L2 cache) implementation based on the
Apache Ignite for different version of hibernate.
The following list of modules we have:
- ignite-hibernate_4.2
- ignite-hibernate_5.1
- ignite-hibernate_5.3
- ignite-hibernate-core (a common part for all hibernate modules)
I propose to use the same approach as was used for the
ignite-spring-data module [1] and move all these modules to the Ignite
Extesions project.
In details:
- remove all these modules from the Ignite project.
- create ignite-hibernate extension.
- move ignite-hibernate-core + ignite-hibernate_4.2 to
release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
extension will be 4.2.0) and release it on demand;
- move ignite-hibernate-core + ignite-hibernate_5.1 to
release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
extension will be 5.1.0) and release it on demand;
- move ignite-hibernate-core + ignite-hibernate_5.3 to the master
branch and to the release/ignite-hibernate-5.3.0 branch (the version
of ignite-hibernate extension will be 5.3.0) and release it
immediately;
Is it OK or am I missing something?
WDYT?
[1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7
Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions
Posted by Maxim Muzafarov <mm...@apache.org>.
Folks,
I've moved the hibernate modules to the Ignite Extension project,
however, we can't deploy them to the Maven Central since they have the
LGPL dependencies. This is also mentioned in the documentation [1].
Users must build them manually from the sources to use.
Another problem I've faced with - there is a lot of manual work to
include required extension to the Ignite binary distribution (e.g.
build an extension, copy libs etc.). We should provide an ability to
build and prepare the Ignite binary distribution with the extension we
need. The same way as the dependencies-apache-ignite-lgpl.xml does.
I've created an issue for that [2].
[1] https://ignite.apache.org/docs/latest/setup#enabling-modules
[2] https://issues.apache.org/jira/browse/IGNITE-16981
On Thu, 28 Apr 2022 at 15:43, Maxim Muzafarov <mm...@apache.org> wrote:
>
> Folks,
>
> I've created a task:
> https://issues.apache.org/jira/browse/IGNITE-16908
>
> On Tue, 26 Apr 2022 at 23:16, Nikita Amelchev <na...@apache.org> wrote:
> >
> > +1
> >
> > вт, 26 апр. 2022 г. в 17:22, Anton Vinogradov <av...@apache.org>:
> > >
> > > +1
> > >
> > > On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков <ni...@apache.org> wrote:
> > >
> > > > +1
> > > >
> > > > > 26 апр. 2022 г., в 16:24, Maxim Muzafarov <mm...@apache.org>
> > > > написал(а):
> > > > >
> > > > > Hello Igniters,
> > > > >
> > > > >
> > > > > Currently we have a batch of ignite-hibernate modules which provide
> > > > > Hibernate second-level cache (L2 cache) implementation based on the
> > > > > Apache Ignite for different version of hibernate.
> > > > >
> > > > > The following list of modules we have:
> > > > > - ignite-hibernate_4.2
> > > > > - ignite-hibernate_5.1
> > > > > - ignite-hibernate_5.3
> > > > > - ignite-hibernate-core (a common part for all hibernate modules)
> > > > >
> > > > > I propose to use the same approach as was used for the
> > > > > ignite-spring-data module [1] and move all these modules to the Ignite
> > > > > Extesions project.
> > > > >
> > > > > In details:
> > > > >
> > > > > - remove all these modules from the Ignite project.
> > > > > - create ignite-hibernate extension.
> > > > > - move ignite-hibernate-core + ignite-hibernate_4.2 to
> > > > > release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
> > > > > extension will be 4.2.0) and release it on demand;
> > > > > - move ignite-hibernate-core + ignite-hibernate_5.1 to
> > > > > release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
> > > > > extension will be 5.1.0) and release it on demand;
> > > > > - move ignite-hibernate-core + ignite-hibernate_5.3 to the master
> > > > > branch and to the release/ignite-hibernate-5.3.0 branch (the version
> > > > > of ignite-hibernate extension will be 5.3.0) and release it
> > > > > immediately;
> > > > >
> > > > >
> > > > > Is it OK or am I missing something?
> > > > > WDYT?
> > > > >
> > > > >
> > > > > [1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7
> > > >
> > > >
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions
Posted by Maxim Muzafarov <mm...@apache.org>.
Folks,
I've created a task:
https://issues.apache.org/jira/browse/IGNITE-16908
On Tue, 26 Apr 2022 at 23:16, Nikita Amelchev <na...@apache.org> wrote:
>
> +1
>
> вт, 26 апр. 2022 г. в 17:22, Anton Vinogradov <av...@apache.org>:
> >
> > +1
> >
> > On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков <ni...@apache.org> wrote:
> >
> > > +1
> > >
> > > > 26 апр. 2022 г., в 16:24, Maxim Muzafarov <mm...@apache.org>
> > > написал(а):
> > > >
> > > > Hello Igniters,
> > > >
> > > >
> > > > Currently we have a batch of ignite-hibernate modules which provide
> > > > Hibernate second-level cache (L2 cache) implementation based on the
> > > > Apache Ignite for different version of hibernate.
> > > >
> > > > The following list of modules we have:
> > > > - ignite-hibernate_4.2
> > > > - ignite-hibernate_5.1
> > > > - ignite-hibernate_5.3
> > > > - ignite-hibernate-core (a common part for all hibernate modules)
> > > >
> > > > I propose to use the same approach as was used for the
> > > > ignite-spring-data module [1] and move all these modules to the Ignite
> > > > Extesions project.
> > > >
> > > > In details:
> > > >
> > > > - remove all these modules from the Ignite project.
> > > > - create ignite-hibernate extension.
> > > > - move ignite-hibernate-core + ignite-hibernate_4.2 to
> > > > release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
> > > > extension will be 4.2.0) and release it on demand;
> > > > - move ignite-hibernate-core + ignite-hibernate_5.1 to
> > > > release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
> > > > extension will be 5.1.0) and release it on demand;
> > > > - move ignite-hibernate-core + ignite-hibernate_5.3 to the master
> > > > branch and to the release/ignite-hibernate-5.3.0 branch (the version
> > > > of ignite-hibernate extension will be 5.3.0) and release it
> > > > immediately;
> > > >
> > > >
> > > > Is it OK or am I missing something?
> > > > WDYT?
> > > >
> > > >
> > > > [1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7
> > >
> > >
>
>
>
> --
> Best wishes,
> Amelchev Nikita
Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions
Posted by Nikita Amelchev <na...@apache.org>.
+1
вт, 26 апр. 2022 г. в 17:22, Anton Vinogradov <av...@apache.org>:
>
> +1
>
> On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков <ni...@apache.org> wrote:
>
> > +1
> >
> > > 26 апр. 2022 г., в 16:24, Maxim Muzafarov <mm...@apache.org>
> > написал(а):
> > >
> > > Hello Igniters,
> > >
> > >
> > > Currently we have a batch of ignite-hibernate modules which provide
> > > Hibernate second-level cache (L2 cache) implementation based on the
> > > Apache Ignite for different version of hibernate.
> > >
> > > The following list of modules we have:
> > > - ignite-hibernate_4.2
> > > - ignite-hibernate_5.1
> > > - ignite-hibernate_5.3
> > > - ignite-hibernate-core (a common part for all hibernate modules)
> > >
> > > I propose to use the same approach as was used for the
> > > ignite-spring-data module [1] and move all these modules to the Ignite
> > > Extesions project.
> > >
> > > In details:
> > >
> > > - remove all these modules from the Ignite project.
> > > - create ignite-hibernate extension.
> > > - move ignite-hibernate-core + ignite-hibernate_4.2 to
> > > release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
> > > extension will be 4.2.0) and release it on demand;
> > > - move ignite-hibernate-core + ignite-hibernate_5.1 to
> > > release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
> > > extension will be 5.1.0) and release it on demand;
> > > - move ignite-hibernate-core + ignite-hibernate_5.3 to the master
> > > branch and to the release/ignite-hibernate-5.3.0 branch (the version
> > > of ignite-hibernate extension will be 5.3.0) and release it
> > > immediately;
> > >
> > >
> > > Is it OK or am I missing something?
> > > WDYT?
> > >
> > >
> > > [1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7
> >
> >
--
Best wishes,
Amelchev Nikita
Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions
Posted by Anton Vinogradov <av...@apache.org>.
+1
On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков <ni...@apache.org> wrote:
> +1
>
> > 26 апр. 2022 г., в 16:24, Maxim Muzafarov <mm...@apache.org>
> написал(а):
> >
> > Hello Igniters,
> >
> >
> > Currently we have a batch of ignite-hibernate modules which provide
> > Hibernate second-level cache (L2 cache) implementation based on the
> > Apache Ignite for different version of hibernate.
> >
> > The following list of modules we have:
> > - ignite-hibernate_4.2
> > - ignite-hibernate_5.1
> > - ignite-hibernate_5.3
> > - ignite-hibernate-core (a common part for all hibernate modules)
> >
> > I propose to use the same approach as was used for the
> > ignite-spring-data module [1] and move all these modules to the Ignite
> > Extesions project.
> >
> > In details:
> >
> > - remove all these modules from the Ignite project.
> > - create ignite-hibernate extension.
> > - move ignite-hibernate-core + ignite-hibernate_4.2 to
> > release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
> > extension will be 4.2.0) and release it on demand;
> > - move ignite-hibernate-core + ignite-hibernate_5.1 to
> > release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
> > extension will be 5.1.0) and release it on demand;
> > - move ignite-hibernate-core + ignite-hibernate_5.3 to the master
> > branch and to the release/ignite-hibernate-5.3.0 branch (the version
> > of ignite-hibernate extension will be 5.3.0) and release it
> > immediately;
> >
> >
> > Is it OK or am I missing something?
> > WDYT?
> >
> >
> > [1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7
>
>
Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions
Posted by Николай Ижиков <ni...@apache.org>.
+1
> 26 апр. 2022 г., в 16:24, Maxim Muzafarov <mm...@apache.org> написал(а):
>
> Hello Igniters,
>
>
> Currently we have a batch of ignite-hibernate modules which provide
> Hibernate second-level cache (L2 cache) implementation based on the
> Apache Ignite for different version of hibernate.
>
> The following list of modules we have:
> - ignite-hibernate_4.2
> - ignite-hibernate_5.1
> - ignite-hibernate_5.3
> - ignite-hibernate-core (a common part for all hibernate modules)
>
> I propose to use the same approach as was used for the
> ignite-spring-data module [1] and move all these modules to the Ignite
> Extesions project.
>
> In details:
>
> - remove all these modules from the Ignite project.
> - create ignite-hibernate extension.
> - move ignite-hibernate-core + ignite-hibernate_4.2 to
> release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
> extension will be 4.2.0) and release it on demand;
> - move ignite-hibernate-core + ignite-hibernate_5.1 to
> release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
> extension will be 5.1.0) and release it on demand;
> - move ignite-hibernate-core + ignite-hibernate_5.3 to the master
> branch and to the release/ignite-hibernate-5.3.0 branch (the version
> of ignite-hibernate extension will be 5.3.0) and release it
> immediately;
>
>
> Is it OK or am I missing something?
> WDYT?
>
>
> [1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7