jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2 & 3
  • MNG-426

[toolchain] create "maxmem" setting for all plugins to refer to

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: 3.1
  • Component/s: Settings
  • Labels:
    None

Description

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.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MCOMPILER-18 add maxmem and meminitial settings when forking

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
David Hoffer added a comment - 12/May/06 7:12 AM

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.

Show
David Hoffer added a comment - 12/May/06 7:12 AM 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.
Hide
Permalink
Brett Porter added a comment - 15/Jun/07 9:13 AM

filing under settings - this is relevant to toolchain support

Show
Brett Porter added a comment - 15/Jun/07 9:13 AM filing under settings - this is relevant to toolchain support
Hide
Permalink
John Casey added a comment - 09/Feb/09 9:35 AM

Consolidating to 2.1.0-M1 so we can then rename to 2.1.0. We can weed out any issues we want to push to a later release from this set once we've done the consolidation.

Show
John Casey added a comment - 09/Feb/09 9:35 AM Consolidating to 2.1.0-M1 so we can then rename to 2.1.0. We can weed out any issues we want to push to a later release from this set once we've done the consolidation.

People

  • Assignee:
    Unassigned
    Reporter:
    Jeff Jensen
Vote (6)
Watch (5)

Dates

  • Created:
    23/May/05 7:02 AM
    Updated:
    30/Dec/09 11:36 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.