On 2/5/07, Alastair Maw <[EMAIL PROTECTED]> wrote:
You've evidently been bitten by this and have a set-up that fixes the issue and works, and are therefore reluctant to change it. I respect that and shall now politely stop haranguing you, even if I think I know better. ;)
Note that I'm not opposed to a better build. It is just that your proposal doesn't fit with my requirements *and* experiences as a release builder for Wicket. I have been thinking about forcing the JVM in the plugin section of the 1.4 projects. This is possible, but it is highly installation dependent, and therefore not implemented (yet). I was hoping for a <java>1.4</java> section in the pom, which would then load the corresponding platform or machine dependend settings from either the settings.xml (local configuration) or the defaults from some obscure maven config file. Martijn -- 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
