Max (and all):
I'm running into this issue too now that I'm reworking some of the unit
tests on classpath containers. The question I have is how best to
configure my example project? Right now it seems to grab from a
hard-coded JRE container.
I guess my question is, can we all look into standardizing a JRE name /
classpath container path that we can all use and expect to run properly
in all of our unit tests? I feel that since this is a common problem we
should all know what our standard is. I'm sure I could analyze it myself
and figure out what will work for me, but I'd prefer if we had some
standard.
- Rob
Max Rydahl Andersen wrote:
The same issue actually exists for the usage of the JRE_CONTAINER:
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/jdk1.5.0_13"/>
Who says that the installed jdk would be jdk1.5.0_13 ?
Please remember that when updating and writing tests.
Thanks!