It is nowadays more than common to have more than one version of a project in the workspace, that support the various versions of the servlet standard (javax.servlet, jakarta.servlet 5.x, and 6.x)

This is typically solved by having various Projects, that all depend on a common core, where the core is agnostic of the servlet API.
In general, that works fine, but the problem here is, that the selection of Tomcat version, and JVM version are global. In other words, the
started Tomcat will, by definition, work for only one of these projects. So, upon switching projects, I need to:

1. Shutdown the running Tomcat.
2. Adjust the global preferences to meet the next projects requirements.
3. Start Tomcat again.

A much better approach would be, if we could have project specific settings for Tomcat, and JVM. (Ideally, we could have several Tomcats running at the same time, in which case we could also need a setting for the port number.)

UI: The classic buttons would still act on the Tomcat from the global preferences. However, if a project has specific settings for Tomcat, or JVM, then the projects context menu would also have entries for starting, and stopping the projects Tomcat.