2013/10/9 Emmanuel Bernard <emmanuel(a)hibernate.org>
No strong opinion.
To me Java 7 is of little value. Java 8 on the other hand...
:)
BTW, will we have trouble with servers that do expect Java 6? I suspect
WF is already on 7 so we don't have that problem on that side.
Yes, WF as EE 7 container must "provide all application components with at
least the Java Platform, Standard Edition, v7 (Java SE) APIs." (as per the
EE spec, 6.1.1).
Emmanuel
On Wed 2013-10-09 13:55, Gunnar Morling 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(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev