Bug 45899 - Make build in separate VM the default setting for Ant launch configs
Summary: Make build in separate VM the default setting for Ant launch configs
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M5   Edit
Assignee: Jared Burns CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-31 18:14 EST by Darin Swanson CLA
Modified: 2003-11-19 17:54 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Swanson CLA 2003-10-31 18:14:01 EST 
Instead of the current behavior of having Ant builds occur by default in the 
same VM as Eclispe we should build in separate VM by default.
Comment 1 Darin Swanson CLA 2003-11-17 19:22:23 EST 
The default settings are now to perform the Ant build in a separate VM.
The default VM install is that of the project associated with the Ant build 
launch config or the workspace default VM install is used if no project is 
available.
Comment 2 Darin Swanson CLA 2003-11-17 19:46:27 EST 
Please verify changes to AntJRETab, AntTabGroup and AntLaunchShortcut, Jared.
Comment 3 Jared Burns CLA 2003-11-17 21:16:29 EST 
I notice that you also removed a line in AntJRETab that was setting 
ATTR_VM_INSTALL_TYPE_SPECIFIC_ATTRS_MAP to null. It looks like this code was 
just removed; I don't see this attribute being set elsewhere in the changed 
code. Was it a separate bug?
Comment 4 Darin Swanson CLA 2003-11-17 22:36:48 EST 
Good catch :-)

Somewhat a separate bug.
The VM args, dynamic tab arguments and working directory arguments are 
retained but only used if the build is set to occur in a separate VM.
The VM args and working dir were previously retained.
I was fixing up the the dynamic tab args to match.
Comment 5 Jared Burns CLA 2003-11-19 17:54:53 EST 
Verified.