Johan Compagner wrote: > This is a bit horrible, > If i do that then on some projects who needs java5 it uses java4, so thats > the first thing i need to change.
It should properly pick up to use 1.4 JDK to compile against, at least, but not for the JRE lib to link against. I might see what is required to sort this out and cook up an Eclipse plug-in that runs eclipse:eclipse and then tweaks it to use a 1.4 JDK if available as the JRE container to link against. > But the worse part is that i then also have to go over every project and > delete the wicket.jar (and the wicket-extentions.jar when used) > and assign the project :( You shouldn't have to do that unless you're running mvn eclipse:eclipse on each project individually. You should be able to mvn eclipse:eclipse on the top-level and have it pull in the project deps properly. I'm off to test this, but it was working fine the other day. Al
