On Mon, Jan 13, 2020 at 7:21 PM Vangel V. Ajanovski <ajanov...@gmail.com> wrote:
> I am using Tapestry to develop applications for internal research and > teaching purposes, Nice! > and have recently migrated two applications that are > used daily to 5.5.0-beta-3 and they are running without issues on Java 12. > I have tried running on Java 13 but it was not possible, due to > unsupported class versions. > As far as I know, Java 12 doesn't have any bytecode differences to 11, so supporting 11 also supports 12. 13, on the other hand, does introduce new bytecode. This is a known issue and my plan is to support Java 14 (LTS version soon to be released) in Tapestry 5.6 (which shouldn't take as long to be released as 5.5). It's not trivial to support a new Java bytecode version in Tapestry because this is done by embedding (i.e. copying and then changing the package name) the ASM sources and then applying a couple of manual changes. > As the documentation indicates that Java 11 is the supported version, I > wanted to ask the reason for this. Is it just because 11 is LTS? Yes. > Or there are truly some specific cases that I have not encountered which > prevent fully supported operation under Java 12 and I have to be careful. > I don't know any. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
