Community
Participate
Working Groups
Build 20030520 Assuming cross-development is quite a rare scenario, our default behavior should likely be to have a consistent set of settings for compile-time and runtime. In particular, JDK levels should be checked at some point. i.e. when user switches from using a different installed JRE for a given project, some checking should occur to see whether the project compile settings are consistent (if picking a 1.4 JRE, it is likely the user should be prompted to flip into 1.4 compliant mode as well).
In the default case the build and run-time JDK are the same (launch configs use the default workspace JDK) and we are OK for the common case. However, I agree that checking matching JDK levels would be nice. Moving to jdt-debug
Note that now JDT/Core optionally checks usage of incompatible binaries (when target JDK is lesser than some required libraries version). But this is only one facet of the various issues.
Nothing planned at this time. Currently there is no API to support this across VM installs - which can be client provided via an extension.
closing - we have execution environments now.
marking as won't fix.
