Could be a problem for enterprise apps. Organisations are slow to move. e.g. we would be forced to move from weblogic 11g to weblogic 12g and then have to enter the brain dead "N-1" debate.
________________________________ From: Dan Haywood <[email protected]> To: users <[email protected]> Sent: Saturday, 12 October 2013 12:23 AM Subject: Re: [DISCUSSION] should Isis drop JDK 1.6 support? This change in Isis would require that you run Tomcat under JDK 1.7. Java is backwardly compatible, so a JDK 1.7 VM will run stuff compiled to Java 1.6. But it would mean that your deployment environment is 1.7. Is that doable for you... easy enough to verify, I would guess? On 11 October 2013 12:19, GESCONSULTOR - Óscar Bou <[email protected]>wrote: > > Our current viewer technology runs on java 1.6. Can it be a problem if > running on Tomcat together? > > > El 11/10/2013, a las 13:16, Mike Burton <[email protected]> > escribió: > > > +1 > > > > > > On 11 Oct 2013, at 12:08, Martin Grigorov <[email protected]> wrote: > > > >> +1 > >> > >> > >> On Fri, Oct 11, 2013 at 1:59 PM, Dan Haywood > >> <[email protected]>wrote: > >> > >>> Several reasons: > >>> > >>> 1. Martin Grigorov (Wicket committer) and Michael Haitz (similar Wicket > >>> expert) are working on ISIS-537 [1] to restyle Wicket using Bootstrap3. > >>> One of their key dependencies is currently only available under JDK > 1.7. > >>> > >>> 2. Wicket 7.0 will mandate JDK 1.7, and, obviously Isis' Wicket viewer > >>> should keep up with the latest version of Wicket. > >>> > >>> 3. its 2013 already. > >>> > >>> > >>> Any votes +1 or -1? > >>> > >>> Thx > >>> Dan > >>> > >>> > >>> [1] https://github.com/l0rdn1kk0n/isis/commits/ISIS-537 > >>> > > > >
