[hibernate-dev] [OGM] Requiring Java 7?

[Steve Ebersole]

What is gained needs to be balanced by what you are giving up.

OGM itself is new, but at the end of the day its a JPA provider which is 
not new.  Basing on Java 7 will limit adaption from folks wanting to 
drop OGM in to their app as replacement for their JPA provider to give 
it a spin in certain environments.

On 10/09/2013 07:54 AM, Sanne Grinovero wrote:
> +1 for requiring Java7
>
> On 9 October 2013 12:55, Gunnar Morling <gunnar at hibernate.org> wrote:
>> Hi,
>>
>> In the context of the notorious JavaDoc CSS issue ([OGM-341] - an updated
>> stylesheet is required when building our projects with Java 7) Sanne,
>> Davide and I were wondering whether we should take the opportunity and
>> actually require Java 7 as the minimum version for Hibernate OGM, not only
>> at build but also at run time.
>>
>> This would give us some interesting opportunities for the implementation,
>> language-wise (e.g. diamond operator, multi-catch) as well as library-wise
>> (e.g. the fork/join framework). On the downside we might exclude some users
>> who are still running on Java 6.
>>
>> Given that OGM is a rather new project, I'd assume though that at this
>> point most users are in a more experimental stage of using it. I'd thus
>> also expect that they use a more current version than 6 which has reached
>> the end of its (public) support lifecycle. So this change might not effect
>> many in reality.
>>
>> Any thoughts?
>>
>> --Gunnar
>>
>> [OGM-341] https://hibernate.atlassian.net/browse/OGM-341
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev