On 16/06/2023 09:07, Rémy Maucherat wrote:
On Thu, Jun 15, 2023 at 9:54 PM Mark Thomas <ma...@apache.org> wrote:
On 15/06/2023 19:23, Joel Griffith wrote:
It looks like the JDT you mention is the Ubuntu package
`libeclipse-jdt-core-java`.
When I installed Tomcat 9 (9.0.31) on the functioning Ubuntu 20.04 system,
version 3.18.0+eclipse4.12-1 of this JDT package was installed as a
dependency. When I installed Tomcat 9 (9.0.58) on the Ubuntu 22.04 system,
version 3.27.0+eclipse4.21-1 was installed. Assuming the "4.12" and "4.21"
numbers are the JDT versions you're referring to, it seems like you're
right about the cause.
According to this table (https://tomcat.apache.org/whichversion.html),
Tomcat 9 is supposed to be compatible with Java 8, yet in this case it
seems to have broken compatibility on a patch update between 9.0.31 and
9.0.58. In order to regain compatibility, the dependency on JDT should be
adjusted to a lower version. Is this something the Tomcat people have to
handle, or is it the package maintainers at Canonical who make that choice?
That would be Canonical.
If you get Tomcat 9 from the ASF it works out of the box on Java 8. (You
actually get the reverse issue with really new JDKs and very old JDTs
but that isn't what is happening here).
JDT seems to be getting more and more aggressive with bumping Java
requirements. For example, Tomcat 10.1 uses Java 11 as the minimum,
but JDT 4.28 is *already* Java 17+. So Tomcat 10.1 will stay on 4.27
forever basically.
Thanks for the info. I hadn't realized that. I guess I would have found
out when I did the version updates for the July releases. I've added a
note to the 10.1.x build.properties file.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
