You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Hoffer (JIRA)" <ji...@codehaus.org> on 2006/05/12 14:12:41 UTC
[jira] Commented: (MNG-426) Create "maxmem" setting for all plugins
to refer to
[ http://jira.codehaus.org/browse/MNG-426?page=comments#action_65279 ]
David Hoffer commented on MNG-426:
----------------------------------
I would think there would be a centralized value that gets used as the default, but if a pom specifies a value it should be used instead.
> Create "maxmem" setting for all plugins to refer to
> ---------------------------------------------------
>
> Key: MNG-426
> URL: http://jira.codehaus.org/browse/MNG-426
> Project: Maven 2
> Type: New Feature
> Reporter: Jeff Jensen
> Fix For: 2.1
>
>
> Create a centralized setting for the max memory setting that all plugins launching a new JVM to respect/use. Then, update the plugins to use it.
> With the time spent repeatedly running, researching, and configuring some plugins to not have "Out of Memory" errors, it now seems silly not to add this kind of feature in the revolutionary vs evolutionary Maven 2! :-)
> I would prefer a setting at the core Maven level, e.g. maven.plugins.maxheap=1024m, that the plugins "magically" used, vs having to repeatedly specify the same one to each plugin that needs it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira