On Fri, Jan 22, 2016 at 8:31 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote:
> Regarding requiring Java 8 for 5.5, I think we need to discuss what are > the pros and cons and then check the cost-benefit ratio. So far, Java 6 is > required. Unfortunately, some companies are still stuck with pre-8 Java > versions, even if 7 was already end-of-lined in April 2015 ( > http://www.oracle.com/technetwork/java/eol-135779.html). I'm not against > it. Java 8 is great. It's just about not imposing a requirement without > disregarding the consequences. I recently worked at a place (hi Bob!) that finally got all of their developers off Java 6 (there were some stragglers due to hardware issues). Given that Tapestry 5.5 won't be out for a bit, I think Java 7 as a minimum would be quite acceptable to most end users and would not prohibit them from using Java 8+ for their Tapestry development/deployment while still supporting those "stuck" on Java 7. Generally, I think it is better for a framework to support an older Java version for greater compatibility with the user base, even if the majority of the user community is using a higher version. Thanks, mrg
