From my perspective, this is the same concept as the port settings -
provide some basic defaults and let users change them with patches. If I
want to enable memory dumps on my local copy, then I can apply a patch
that turns them on.
Indeed, I have a patch called local-dev that configures a num
OK you are both right (though I don't think this one does not put any harms on
performance or ressources).
Then we need a mean to pass parameters through ant start target :
http://ant.apache.org/manual/Tasks/property.html
Jacques
From: "Jacopo Cappellato"
Yeah,
there are several -XX parame
Yeah,
there are several -XX parameters that are useful when you analyze issues or
memory leaks etc... but it doesn't mean that they have to be enabled by default.
Jacopo
On Apr 29, 2012, at 11:36 PM, Pierre Smits wrote:
> Jacques,
>
> I agree that setting the HeadDumpOnOutOfMemmoryError occas
Jacques,
I agree that setting the HeadDumpOnOutOfMemmoryError occasionally can
prove usefull, but shouldn't an update of document be enough to create
the awareness?
Adding the code change kinda contradicts your statement and makes it
permanent and always on
Regards,
Pierre
2012/4/29 :
> Autho
