I think we should definitely move to Java 7 for Infinispan 6.0.
Coincidentally, I've been packaging netty 3.6.x which needs java 7 to
build but generates Java 6-compatible bytecode using various maven
plugins to perform the magic, which could be used as an interim solution.
Tristan
On 02/08/2013 09:29 AM, Galder Zamarreño wrote:
Thoughts?
Begin forwarded message:
> *From: *Brian Oliver <brian.oliver(a)oracle.com
> <mailto:brian.oliver@oracle.com>>
> *Subject: **Moving to Java 7?*
> *Date: *February 5, 2013 9:13:35 PM GMT+01:00
> *To: *jsr107(a)googlegroups.com <mailto:jsr107@googlegroups.com>
> *Reply-To: *jsr107(a)googlegroups.com <mailto:jsr107@googlegroups.com>
>
> Currently we are targeting Java 7 for JSR-107.
>
> Given that:
>
> a). Java 6 is end-of-life at the end of February 2013 (see
>
http://www.oracle.com/technetwork/java/eol-135779.html)
> b). We're meant to be working with Java EE 7 (ok, we've slipped but
> Java EE7 is Java 7+)
>
> I'd like to propose Java 7 as the minimum requirement for JSR-107
> (although it may work on Java 6, we just wouldn't guarantee it).
>
> Thoughts?
>
> -- Brian
>
> --
> You received this message because you are subscribed to the Google
> Groups "jsr107" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to jsr107+unsubscribe(a)googlegroups.com
> <mailto:jsr107+unsubscribe@googlegroups.com>.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>
--
Galder Zamarreño
galder(a)redhat.com <mailto:galder@redhat.com>
twitter.com/galderz <
http://twitter.com/galderz>
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev