I have complained about this many times... On 2024/02/12 20:58:14 Christopher Schultz wrote: > All, > > The release managers have bumped-up their tool chains to Java 17 or > later for all supported releases. Tomcat 11 requires Java 21. Tomcat > 8.5.x only requires Java 11. > > But the documented Java versions for each release are actually: > > Tomcat 11 - Java 21 > Tomcat 10 - Java 11 > Tomcat 9 - Java 8 > Tomcat 8 - Java 7 > > Theoretically, anyone ought to be able to build Tomcat with the > minimum-required Java version for that branch. There are some practical > reasons why you can't build Tomcat 8.5.x with Java 7 but those have more > to do with supporting versions of Java *after* 7 than anything else. > > I'd like to be able to allow anyone to build their Tomcat from source > using our tooling (e.g. ant-based build) and the minimum Java version > (with one exception: No support for Java 7 for builds). > > Take Tomcat 9.0.x for example. The ant-based build will complain if you > are using Java 11 to build, because the build tools demand the use of > Java 17. If you simply change the "required version" from 17 to 11, the > build works perfectly fine.
No, it won't. I have written exactly this last week. BND is now at version 7.0 which requires Java 17at runtime. I have downgraded manually to 6.4.0 to test on HP-UX with Tomcat Native 1.3.x. For the sake of latest BND I don't see a strong reason to force Java 17, especially for those who want to test... My overall opinion is to impose the oldest required version to build and test it. (not talking about release). Michael PS: Thank for raising, Chris! --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
