It was slightly different in the previous template:
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> Which takes the default JRE.
The addition of "/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5" signals to select a Java 1.5 JRE/JDK. If no matching JRE/JDK5 is installed, then it still selects the JRE6 (or simply the best match it can find from the list of installed JREs), so I thought it doesn't hurt.
Well, doesn't the fact that Eclipse falls back to 1.6 (or the best
available match) for J2SE-1.5 in the absence of a perfect match defeat
the usefulness of the addition in a way?
But still, the missing JDK warning from IntelliJ is IMHO correct: If we target Java 1.5, then we should compile against it. Otherwise it leads into believing that an API can be used because of the 1.6 JDK and Javadoc while in fact it cannot (e.g. the JDialog constructor bug which accepts null in 1.6 but doesn't in 1.5).
I still have to install a perfect match for J2SE-1.5 in order to make
use of the automatic protection from using unavailable API.
In light of the problem that it creates for IntelliJ IDEA, I'd vote
the addition down because I find the line between its advantages and
2011/11/30 Bauersachs Ingo <email@example.com>: