Bugzilla – Full Text Bug Listing
| Summary: | [launching] launch config vm arguments should override JRE default arguments | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Tom Hofmann <eclipse> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Michael_Rennie |
| Version: | 3.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux-GTK | ||
| Whiteboard: | |||
Deferred As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. Marking as dupe of 217994 because there is patch on that bug *** This bug has been marked as a duplicate of bug 217994 *** |
N20060426 - I have a JRE configured with a default argument of -Xmx512m - In a specific launch config, I spec a VM argument of -Xmx256m > expected: the launch config's argument override the default arguments. < actual: the launch config's argument is superseded by the default arguments - the command line reads: ...java -Xmx256m -Xmx512M -classpath ... The luxury solution would remove the default argument if a similar argument is in the launch config. At least, the launch config's arguments should be on the command line *after* the default args.