Verify if we have any obvious issues with Java5/Java6 combinations

EAP 5 will most likely be a Java 6 only runtime, thus we need to verify the following:

So we should get QA to try and run at least some basic testing on a few scenarioes:
A) Run JBDS on Java 5 but target Java 6 EAP (which should work fine)

B) Same as A, but now try using Hibernate Tools on the project - HT loads classes inside Eclipse VM so will that cause problems (Java 5 runtime loading classes from EAP 5 with Java 6 compiled classes) - try code generation, HQL querying etc.

C) Run JBDS on Java 6 and target Java 6 EAP - try use hibernate tools/seam

If Point B is an issue I don't see us fixing this in this release unless C is impossilbe (but I haven't seen that be a problem), it will be a known limitation to be fixed in JBDS 3 then.