I think I was the one that changed the batch file to use MAVEN_DEFAULT_OPTS and MAVEN_OPTS, and I wasn't trying to be tricky, I was trying to get a solution.Isn't this what MAVEN_OPTS is for?
The user can set stuff in MAVEN_OPTS and override the defaults....
hum... are you saying that the following works:
java -Xmx160m -Xmx256m [...]
?
Even if it works, it doesn't look like a valid solution but more like a trick to me. What do you think?
It seemed to work for me, so I committed it. It also allows running of maven in a debugger etc, so I'd rather not get rid of the functionality.
Normally maven site wont work without a fair chunk of memory, and the defaults didn't work, hence MAVEN_DEFAULT_OPTS.
Back to the original point, I can't see why the user should have to change the batch file....
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
