All,
Tomcat has to be built, tested, and deployed in a variety of
environments. Specifically, in a variety of Java Runtime Environments.
I'm finding that my 8.5.x testing and execution requires some weird
backflips due to JDT versioning.
Would be make any sense to ship Tomcat with several versions of the jdt
compiler and then load the one most-appropriate for the JRE at runtime?
Maybe this really only affects me in my capacity as release-manager and
tester (and user!) of 8.5.x, but I suspect it affects others as well.
The error messages make no sense whatsoever. For example,
"NoSuchClassDefFoundError: java.lang.System" is a great one. I know the
problem is that the jdt is inappropriate for that version of the JRE,
but ... would most users be able to figure that out?
I don't think it would be that onerous to auto-detect at runtime and
install an appropriate jdt, though I haven't even looked at what
versions are available, what their target JREs are, etc. I think it
would be helpful to downstream users if we picked the right jdt for them
at runtime.
WDYT?
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
