+1 However, just a reminder, most environments (e.g. Java EE application servers: WebSphere, WebLogic, etc) where GemFire/Geode will most likely be used (in the enterprise) are still largely based on a 1.6 runtime, especially older versions that are still predominantly in production.
In addition, Oracle has pushed out the release date of Java EE 8 <https://blogs.oracle.com/theaquarium/entry/java_ee_8_roadmap_update> [0]. It is also worth mentioning that "*end of public updates*" (Java 7 - April 2015) does not mean "*end of life*" (Java 7 - July 2022). Even 1.6 will have extended support until December 2018! See Oracle commercial offerings doc <http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings> [1] for further details. It is more likely that companies will purchase "extended support" than it is for them to completely supplant their existing infrastructure. The migration process is long and cumbersome for most enterprise customers, especially banks, etc. So, for Geode, this effectively means we could limit our audience out of the gate. [0] - https://blogs.oracle.com/theaquarium/entry/java_ee_8_roadmap_update [1] - *http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings <http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings>* On Fri, Oct 23, 2015 at 10:36 AM, Bruce Schuchardt <[email protected]> wrote: > +1 > > Let's move to Java 8! > > > Le 10/23/2015 9:27 AM, William Markito a écrit : > >> Folks, >> >> We had some discussions around this in the past but I guess we have not >> yet >> made the decision to move forward and change the language level. >> >> Just opened GEODE-479 and would like to propose to do this change before >> our Alpha release. >> >> Any thoughts ? >> > > -- -John 503-504-8657 john.blum10101 (skype)
