On 12 July 2017 16:33:01 CEST, Matt Sicker <[email protected]> wrote: >Are there plans to require 1.7 for Tomcat anytime? Otherwise, it might >be >necessary to make a new major version of daemon eventually for Java 8 >or 9.
Tomcat major versions are aligned with Java EE versions which in turn have a minimum Java version. Tomcat supports 3 current versions in parallel so we currently have: Tomcat 9 - Java EE 8 - Java 8 Tomcat 8 - Java EE 7 - Java 7 Tomcat 7 - Java EE 6 - Java 6 Tomcat 7 support will continue until at least Java EE 9 is released. That is meant to be next year but there are no firm dates yet and experience suggests the Java EE 9 release date will slip. On that basis I expect Tomcat to need a Daemon that supports Java 6 for at least 2 more years. Is there a user requirement driving an increase in the minimum Java version? If not, I suggest we stick with 6 for now. Mark > >Anyways, 1.6 minimum makes sense to me mainly due to Java 9's compiler >not >supporting Java 5 targets anymore. > >On 12 July 2017 at 09:19, Mark Thomas <[email protected]> wrote: > >> On 11 July 2017 21:02:54 CEST, Amey Jadiye <[email protected]> >wrote: >> >Hi Daemon Maintainers / All, >> > >> >Daemon seems to be still being maintained on svn, do we have any >plan >> >moving code base to git ? >> >> No preference on this. >> >> >As fact there is low activity in daemon no one thought of bumping >> >version >> >from 1.5 to 1.6 OR we are keeping it purposefully to 1.5 ? >> >shall we bump it minimum to 1.6 ? >> >> 1.6 is OK for Tomcat. Anything higher will cause problems. >> >> Mark >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
