I'm with Kalle as well, 1.6 is more than reasonable, and maybe 1.8 for 5.5 (which I really hope will be very quick, just clearing out deprecated code and upgrading to JDK 1.7 or 1.8).
On Wed, May 14, 2014 at 7:27 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Fri, 02 May 2014 04:45:42 -0300, Ulrich Stärk <u...@spielviel.de> wrote: > > Do you expect any problems if we just switched to Java 8/Servlet 3.1 >> without modifying anything else? >> > > Yep. Lots of people and companies that won't or can't upgrade to a Java > version which was just released, at least not in the near future. Not to > mention that Java 8-only features will be only actually known and used by > most people in the not near future. Unless we start using Java 8-only > features in Tapestry, there's no reason IMHO to make such a long jump. The > Tapestry image still has some problems with radical changes. > > I agree with Kalle: "A common sense approach would be to require 1.6 for > T5.4 and then require 1.8 in a future version." > > There's also another possibility: when we do actually use Java 8-only > stuff, for some time, to do it on a branch and release trunk as > tapestry-core without Maven/Gradle qualifiers and this branch with a > "-java8" qualifier. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com @hlship
