I have thought about it and *hard*. The issue is that if I run mvn install, then *EVERYTHING* in my local repo is overwritten with JDK 5 compiled artifacts. That is a definite no go.
The issue is not convenience but ensuring correctness. The only way I can exclude any fuck ups with JDK compilation is using the current setup. And on the Eclipse settings, that just doesn't work. We have had enough issues with that to not trust it. Also, dependencies also need to be JDK 1.4 only otherwise the maven build with JDK 1.4 goes wrong. Again this was only discovered by using the current setup with completely separated builds for 1.4 and 1.5 projects. Martijn On 2/5/07, Al Maw <[EMAIL PROTECTED]> wrote:
Frank Bille wrote: > Yes I agree with Martijn. We really want to catch if any 1.5 stuff is > in 1.4projects. But Al, if you can get maven to do that (forcing > 1.4 in 1.4 projects) it would be nice. I don't know if maven can do that, > though. See my other reply. The thing that matters is what your JAVA_HOME environment is set to. If you're running Maven using a JDK5 on the command line, it doesn't matter what you do - it won't magically pick this up. Which is why we have continuous integration, where we actually run Maven with different JDKs depending on the project. So I'd strongly like you to look at this and understand what I'm saying and reconsider, as I think it'd be a big improvement, with absolutely no difference in picking up backwards-compatibility issues. Al
-- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org
