10:21 a.m.
The next minor release of Apache Lucene v. 4.8 will require Java7.
The Lucene team has highlighted many good reasons for that, including
some excellent improvements in sorting performance and reliability of
IO operations: nice things we'd like to take advantage of.
Objections against baseling Hibernate Search 5 to *require* Java7 too?
We hardly have a choice, so objections better be good ;-)
-- Sanne
10:58 a.m.
On Thu 20 Mar 2014 11:21:23 AM EDT, Sanne Grinovero wrote:
The next minor release of Apache Lucene v. 4.8 will require Java7.
The Lucene team has highlighted many good reasons for that, including
some excellent improvements in sorting performance and reliability of
IO operations: nice things we'd like to take advantage of.
Objections against baseling Hibernate Search 5 to *require* Java7 too?
We hardly have a choice, so objections better be good ;-)
-- Sanne
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Heck, if I weren't careful I'd say move Hibernate to Java *8* -- but
that'd be insane. :) Yes, move it to Java 7.
--
It's not my fault that I can't draw the human posterior with a mouse.
1:20 p.m.
+100
On 20 Jan 2014, at 16:21, Sanne Grinovero <sanne(a)hibernate.org> wrote:
The next minor release of Apache Lucene v. 4.8 will require Java7.
The Lucene team has highlighted many good reasons for that, including
some excellent improvements in sorting performance and reliability of
IO operations: nice things we'd like to take advantage of.
Objections against baseling Hibernate Search 5 to *require* Java7 too?
We hardly have a choice, so objections better be good ;-)
-- Sanne
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
4:40 a.m.
+1
One potential issue coming to mind is that this will require Hibernate OGM
users to work with Java 7 as well (at least when using queries via
Hibernate Search).
When discussing the issue (for OGM) last time, we decided to stick to Java
6 to ease OGM experiments of existing Hibernate ORM users. Personally I
don't think it's a problem, (I had wished to move OGM to Java 7 before),
just pointing out the fact so that there are no surprises.
So once we upgrade OGM to HSEARCH 5.x, I'd then make use of Java 7 features
in OGM as well.
--Gunnar
2014-03-20 19:20 GMT+01:00 Hardy Ferentschik <hardy(a)hibernate.org>:
+100
On 20 Jan 2014, at 16:21, Sanne Grinovero <sanne(a)hibernate.org> wrote:
> The next minor release of Apache Lucene v. 4.8 will require Java7.
>
> The Lucene team has highlighted many good reasons for that, including
> some excellent improvements in sorting performance and reliability of
> IO operations: nice things we'd like to take advantage of.
>
> Objections against baseling Hibernate Search 5 to *require* Java7 too?
> We hardly have a choice, so objections better be good ;-)
>
> -- Sanne
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
5:08 a.m.
Since Hibernate OGM is now an implementation of JPA 2.1, doesn't it
already require Java 7?
You could also decide to use Java7 for the build but not necessarily
make use of Java7 features, as Search is an optional dependency. (but
I also don't see a problem on moving).
I would like to encourage OGM to switch to Search 5 soon though: the
HQL parser is aligning already, and some features we're working on in
Search are meant to improve the user experience for OGM users
specifically (HSEARCH-1119), not least it's the version meant for
Infinispan 7, which OGM will need to support a GridDialect over
HotRod. And solid performance improvements as usual ;-)
-- Sanne
On 31 March 2014 10:40, Gunnar Morling <gunnar(a)hibernate.org> wrote:
+1
One potential issue coming to mind is that this will require Hibernate OGM
users to work with Java 7 as well (at least when using queries via Hibernate
Search).
When discussing the issue (for OGM) last time, we decided to stick to Java 6
to ease OGM experiments of existing Hibernate ORM users. Personally I don't
think it's a problem, (I had wished to move OGM to Java 7 before), just
pointing out the fact so that there are no surprises.
So once we upgrade OGM to HSEARCH 5.x, I'd then make use of Java 7 features
in OGM as well.
--Gunnar
2014-03-20 19:20 GMT+01:00 Hardy Ferentschik <hardy(a)hibernate.org>:
> +100
>
> On 20 Jan 2014, at 16:21, Sanne Grinovero <sanne(a)hibernate.org> wrote:
>
> > The next minor release of Apache Lucene v. 4.8 will require Java7.
> >
> > The Lucene team has highlighted many good reasons for that, including
> > some excellent improvements in sorting performance and reliability of
> > IO operations: nice things we'd like to take advantage of.
> >
> > Objections against baseling Hibernate Search 5 to *require* Java7 too?
> > We hardly have a choice, so objections better be good ;-)
> >
> > -- Sanne
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
5:16 a.m.
2014-03-31 12:08 GMT+02:00 Sanne Grinovero <sanne(a)hibernate.org>:
Since Hibernate OGM is now an implementation of JPA 2.1, doesn't
it
already require Java 7?
Good point; Not sure whether JPA 2.1 per-se really requires Java 7, but I
understand as an implementation we'd be "allowed" to require Java 7 as per
the spec guidelines. So far, 6 seemed sufficient for our purposes.
You could also decide to use Java7 for the build but not necessarily
make use of Java7 features, as Search is an optional dependency.
(but
I also don't see a problem on moving).
Yes, I thought about this as well, but it makes a difficult story to
explain (depending on whether you use JP-QL or not, and depending on the
backend you use, you may be use Java 6 or 7). I'd rather move to 7
altogether then and keep things a bit simpler.
I would like to encourage OGM to switch to Search 5 soon though: the
HQL parser is aligning already, and some features we're working on in
Search are meant to improve the user experience for OGM users
specifically (HSEARCH-1119), not least it's the version meant for
Infinispan 7, which OGM will need to support a GridDialect over
HotRod. And solid performance improvements as usual ;-)
+1 :-)
-- Sanne
On 31 March 2014 10:40, Gunnar Morling <gunnar(a)hibernate.org> wrote:
> +1
>
> One potential issue coming to mind is that this will require Hibernate
OGM
> users to work with Java 7 as well (at least when using queries via
Hibernate
> Search).
>
> When discussing the issue (for OGM) last time, we decided to stick to
Java 6
> to ease OGM experiments of existing Hibernate ORM users. Personally I
don't
> think it's a problem, (I had wished to move OGM to Java 7 before), just
> pointing out the fact so that there are no surprises.
>
> So once we upgrade OGM to HSEARCH 5.x, I'd then make use of Java 7
features
> in OGM as well.
>
> --Gunnar
>
>
>
>
> 2014-03-20 19:20 GMT+01:00 Hardy Ferentschik <hardy(a)hibernate.org>:
>
>> +100
>>
>> On 20 Jan 2014, at 16:21, Sanne Grinovero <sanne(a)hibernate.org> wrote:
>>
>> > The next minor release of Apache Lucene v. 4.8 will require Java7.
>> >
>> > The Lucene team has highlighted many good reasons for that, including
>> > some excellent improvements in sorting performance and reliability of
>> > IO operations: nice things we'd like to take advantage of.
>> >
>> > Objections against baseling Hibernate Search 5 to *require* Java7 too?
>> > We hardly have a choice, so objections better be good ;-)
>> >
>> > -- Sanne
>> > _______________________________________________
>> > hibernate-dev mailing list
>> > hibernate-dev(a)lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
9:33 a.m.
http://lists.jboss.org/pipermail/hibernate-dev/2013-February/009426.html
On Mon, Mar 31, 2014 at 5:16 AM, Gunnar Morling <gunnar(a)hibernate.org>wrote:
2014-03-31 12:08 GMT+02:00 Sanne Grinovero
<sanne(a)hibernate.org>:
> Since Hibernate OGM is now an implementation of JPA 2.1, doesn't it
> already require Java 7?
>
Good point; Not sure whether JPA 2.1 per-se really requires Java 7, but I
understand as an implementation we'd be "allowed" to require Java 7 as per
the spec guidelines. So far, 6 seemed sufficient for our purposes.
You could also decide to use Java7 for the build but not necessarily
> make use of Java7 features, as Search is an optional dependency. (but
> I also don't see a problem on moving).
>
Yes, I thought about this as well, but it makes a difficult story to
explain (depending on whether you use JP-QL or not, and depending on the
backend you use, you may be use Java 6 or 7). I'd rather move to 7
altogether then and keep things a bit simpler.
>
> I would like to encourage OGM to switch to Search 5 soon though: the
> HQL parser is aligning already, and some features we're working on in
> Search are meant to improve the user experience for OGM users
> specifically (HSEARCH-1119), not least it's the version meant for
> Infinispan 7, which OGM will need to support a GridDialect over
> HotRod. And solid performance improvements as usual ;-)
>
+1 :-)
>
> -- Sanne
>
> On 31 March 2014 10:40, Gunnar Morling <gunnar(a)hibernate.org> wrote:
> > +1
> >
> > One potential issue coming to mind is that this will require Hibernate
> OGM
> > users to work with Java 7 as well (at least when using queries via
> Hibernate
> > Search).
> >
> > When discussing the issue (for OGM) last time, we decided to stick to
> Java 6
> > to ease OGM experiments of existing Hibernate ORM users. Personally I
> don't
> > think it's a problem, (I had wished to move OGM to Java 7 before), just
> > pointing out the fact so that there are no surprises.
> >
> > So once we upgrade OGM to HSEARCH 5.x, I'd then make use of Java 7
> features
> > in OGM as well.
> >
> > --Gunnar
> >
> >
> >
> >
> > 2014-03-20 19:20 GMT+01:00 Hardy Ferentschik <hardy(a)hibernate.org>:
> >
> >> +100
> >>
> >> On 20 Jan 2014, at 16:21, Sanne Grinovero <sanne(a)hibernate.org>
wrote:
> >>
> >> > The next minor release of Apache Lucene v. 4.8 will require Java7.
> >> >
> >> > The Lucene team has highlighted many good reasons for that,
including
> >> > some excellent improvements in sorting performance and reliability
of
> >> > IO operations: nice things we'd like to take advantage of.
> >> >
> >> > Objections against baseling Hibernate Search 5 to *require* Java7
too?
> >> > We hardly have a choice, so objections better be good ;-)
> >> >
> >> > -- Sanne
> >> > _______________________________________________
> >> > hibernate-dev mailing list
> >> > hibernate-dev(a)lists.jboss.org
> >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>
> >> _______________________________________________
> >> hibernate-dev mailing list
> >> hibernate-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> >
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
11:28 a.m.
On 31 March 2014 15:33, Steve Ebersole <steve(a)hibernate.org> wrote:
Thanks Steve. So I guess that settles it for OGM as well?
(Removed all people from CC as we're changing subject)
-- Sanne
On Mon, Mar 31, 2014 at 5:16 AM, Gunnar Morling <gunnar(a)hibernate.org>
wrote:
>
> 2014-03-31 12:08 GMT+02:00 Sanne Grinovero <sanne(a)hibernate.org>:
>
> > Since Hibernate OGM is now an implementation of JPA 2.1, doesn't it
> > already require Java 7?
> >
>
> Good point; Not sure whether JPA 2.1 per-se really requires Java 7, but I
> understand as an implementation we'd be "allowed" to require Java 7 as
per
> the spec guidelines. So far, 6 seemed sufficient for our purposes.
>
> You could also decide to use Java7 for the build but not necessarily
> > make use of Java7 features, as Search is an optional dependency. (but
> > I also don't see a problem on moving).
> >
>
> Yes, I thought about this as well, but it makes a difficult story to
> explain (depending on whether you use JP-QL or not, and depending on the
> backend you use, you may be use Java 6 or 7). I'd rather move to 7
> altogether then and keep things a bit simpler.
>
> >
> > I would like to encourage OGM to switch to Search 5 soon though: the
> > HQL parser is aligning already, and some features we're working on in
> > Search are meant to improve the user experience for OGM users
> > specifically (HSEARCH-1119), not least it's the version meant for
> > Infinispan 7, which OGM will need to support a GridDialect over
> > HotRod. And solid performance improvements as usual ;-)
> >
>
> +1 :-)
>
>
> >
> > -- Sanne
> >
> > On 31 March 2014 10:40, Gunnar Morling <gunnar(a)hibernate.org> wrote:
> > > +1
> > >
> > > One potential issue coming to mind is that this will require Hibernate
> > OGM
> > > users to work with Java 7 as well (at least when using queries via
> > Hibernate
> > > Search).
> > >
> > > When discussing the issue (for OGM) last time, we decided to stick to
> > Java 6
> > > to ease OGM experiments of existing Hibernate ORM users. Personally I
> > don't
> > > think it's a problem, (I had wished to move OGM to Java 7 before),
> > > just
> > > pointing out the fact so that there are no surprises.
> > >
> > > So once we upgrade OGM to HSEARCH 5.x, I'd then make use of Java 7
> > features
> > > in OGM as well.
> > >
> > > --Gunnar
> > >
> > >
> > >
> > >
> > > 2014-03-20 19:20 GMT+01:00 Hardy Ferentschik <hardy(a)hibernate.org>:
> > >
> > >> +100
> > >>
> > >> On 20 Jan 2014, at 16:21, Sanne Grinovero <sanne(a)hibernate.org>
> > >> wrote:
> > >>
> > >> > The next minor release of Apache Lucene v. 4.8 will require
Java7.
> > >> >
> > >> > The Lucene team has highlighted many good reasons for that,
> > >> > including
> > >> > some excellent improvements in sorting performance and
reliability
> > >> > of
> > >> > IO operations: nice things we'd like to take advantage of.
> > >> >
> > >> > Objections against baseling Hibernate Search 5 to *require* Java7
> > >> > too?
> > >> > We hardly have a choice, so objections better be good ;-)
> > >> >
> > >> > -- Sanne
> > >> > _______________________________________________
> > >> > hibernate-dev mailing list
> > >> > hibernate-dev(a)lists.jboss.org
> > >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > >>
> > >> _______________________________________________
> > >> hibernate-dev mailing list
> > >> hibernate-dev(a)lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > >
> > >
> >
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
4:51 p.m.
2014-03-31 18:28 GMT+02:00 Sanne Grinovero <sanne(a)hibernate.org>:
On 31 March 2014 15:33, Steve Ebersole <steve(a)hibernate.org>
wrote:
> http://lists.jboss.org/pipermail/hibernate-dev/2013-February/009426.html
Thanks Steve. So I guess that settles it for OGM as well?
IIRC, the situation back then was a bit different. The JPA JAR could simply
be made usable with Java 6 as a matter of build configuration, while now a
dependency explicitly requires Java 7.
Sure, we could still support running on Java 6 when not using queries (or
when not using the HSEARCH based parser backend), but given that this is
the default parser backend for all dialects except for MongoDB I doubt that
this is of much use. Also it has been a year since then in which more
projects have been migrating off 6.
Anyways, we had the discussion before and agreed to stick on 6 for OGM for
the time being. When going to HSEARCH 5, we'll require 7 instead in many
cases. That's the effect I wanted to point out to make sure we're all aware
of it. Personally I'd go for 7 altogether, but I'm fine with it either way.
--Gunnar
(Removed all people from CC as we're changing subject)
-- Sanne
>
>
> On Mon, Mar 31, 2014 at 5:16 AM, Gunnar Morling <gunnar(a)hibernate.org>
> wrote:
>>
>> 2014-03-31 12:08 GMT+02:00 Sanne Grinovero <sanne(a)hibernate.org>:
>>
>> > Since Hibernate OGM is now an implementation of JPA 2.1, doesn't it
>> > already require Java 7?
>> >
>>
>> Good point; Not sure whether JPA 2.1 per-se really requires Java 7, but
I
>> understand as an implementation we'd be "allowed" to require Java
7 as
per
>> the spec guidelines. So far, 6 seemed sufficient for our purposes.
>>
>> You could also decide to use Java7 for the build but not necessarily
>> > make use of Java7 features, as Search is an optional dependency. (but
>> > I also don't see a problem on moving).
>> >
>>
>> Yes, I thought about this as well, but it makes a difficult story to
>> explain (depending on whether you use JP-QL or not, and depending on the
>> backend you use, you may be use Java 6 or 7). I'd rather move to 7
>> altogether then and keep things a bit simpler.
>>
>> >
>> > I would like to encourage OGM to switch to Search 5 soon though: the
>> > HQL parser is aligning already, and some features we're working on in
>> > Search are meant to improve the user experience for OGM users
>> > specifically (HSEARCH-1119), not least it's the version meant for
>> > Infinispan 7, which OGM will need to support a GridDialect over
>> > HotRod. And solid performance improvements as usual ;-)
>> >
>>
>> +1 :-)
>>
>>
>> >
>> > -- Sanne
>> >
>> > On 31 March 2014 10:40, Gunnar Morling <gunnar(a)hibernate.org> wrote:
>> > > +1
>> > >
>> > > One potential issue coming to mind is that this will require
Hibernate
>> > OGM
>> > > users to work with Java 7 as well (at least when using queries via
>> > Hibernate
>> > > Search).
>> > >
>> > > When discussing the issue (for OGM) last time, we decided to stick
to
>> > Java 6
>> > > to ease OGM experiments of existing Hibernate ORM users. Personally
I
>> > don't
>> > > think it's a problem, (I had wished to move OGM to Java 7
before),
>> > > just
>> > > pointing out the fact so that there are no surprises.
>> > >
>> > > So once we upgrade OGM to HSEARCH 5.x, I'd then make use of Java
7
>> > features
>> > > in OGM as well.
>> > >
>> > > --Gunnar
>> > >
>> > >
>> > >
>> > >
>> > > 2014-03-20 19:20 GMT+01:00 Hardy Ferentschik
<hardy(a)hibernate.org>:
>> > >
>> > >> +100
>> > >>
>> > >> On 20 Jan 2014, at 16:21, Sanne Grinovero
<sanne(a)hibernate.org>
>> > >> wrote:
>> > >>
>> > >> > The next minor release of Apache Lucene v. 4.8 will require
Java7.
>> > >> >
>> > >> > The Lucene team has highlighted many good reasons for that,
>> > >> > including
>> > >> > some excellent improvements in sorting performance and
reliability
>> > >> > of
>> > >> > IO operations: nice things we'd like to take advantage
of.
>> > >> >
>> > >> > Objections against baseling Hibernate Search 5 to *require*
Java7
>> > >> > too?
>> > >> > We hardly have a choice, so objections better be good ;-)
>> > >> >
>> > >> > -- Sanne
>> > >> > _______________________________________________
>> > >> > hibernate-dev mailing list
>> > >> > hibernate-dev(a)lists.jboss.org
>> > >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> > >>
>> > >> _______________________________________________
>> > >> hibernate-dev mailing list
>> > >> hibernate-dev(a)lists.jboss.org
>> > >> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> > >
>> > >
>> >
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
4283
days inactive
4294
days old
8 comments
5 participants
participants (5)
-
Gunnar Morling -
Hardy Ferentschik -
Joseph B. Ottinger -
Sanne Grinovero -
Steve Ebersole