Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 38263 - Allow separate VM to be controlled at global level for Ant builds
Summary: Allow separate VM to be controlled at global level for Ant builds
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows NT
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 39249 46743 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-05-30 10:32 EDT by Darin Swanson CLA
Modified: 2009-08-30 02:24 EDT (History)
2 users (show)

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-05-30 10:32:45 EDT 
Create a global Ant preference to allow the setting of the default VM for Ant 
builds.

The global setting can be overridden by the per configuration setting
Comment 1 Darin Swanson CLA 2003-05-30 11:56:22 EDT 
We need to work with Java debug to come up with a better story for reuse of the 
JavaJRETab. The JavaJRETab has its own set of problems (needs to be more like 
the InstalledJRE preferencepage).

In Ant land we need to determine the definition of default:
The VM set to build the project?
The global VM set by the user?
In the same VM as Eclipse?
Comment 2 Darin Swanson CLA 2003-06-26 19:32:52 EDT 
*** Bug 39249 has been marked as a duplicate of this bug. ***
Comment 3 Darin Swanson CLA 2003-07-14 13:47:01 EDT 
Pushing back to M3
Comment 4 Darin Wright CLA 2003-07-22 17:08:36 EDT 
I'm wondering if we need an more support that is currently available in 3.0M2. 
Currently you can "run in the same VM", or choose a specific (alternate, 
seperate) VM. The default behavior is to run in the same VM.

Will it be "too complex" to have the following options:
(1) Use default VM (which is controlled by global pref - may be same VM, may be 
alternate)
(2) Use alternamte VM (choose from drop-down)

The current implementation provides all the function. The only drawback is that 
is is inefficient (in user configuration/number of clicks), if you always want 
to use a certain (seperate) VM. Also inefficient if you want to change how all 
your 'default' scripts run - i.e. set them all to use the default VM, and then 
change the VM via a global preference.

Comments? (I'm not sure we know what the common use case is)
Comment 5 Darin Swanson CLA 2003-07-22 17:14:57 EDT 
I have heard from users that they want to easily be able to specify that all 
Ant builds occur in a specific separate VM.
I am hesitant to redefine what "default VM" means in Ant land. I think of the 
default VM as the same VM as Eclipse.
Comment 6 Darin Swanson CLA 2003-08-25 19:30:34 EDT 
Did not make it for M3
Comment 7 Darin Swanson CLA 2003-11-16 17:20:16 EST 
*** Bug 46743 has been marked as a duplicate of this bug. ***
Comment 8 Darin Swanson CLA 2003-11-18 11:12:46 EST 
From M5 on Ant builds will by default occur in a separate VM (see bug 45899).
As such I am lowering the priority on this one and moving to M6 for further 
consideration.
Comment 9 Darin Swanson CLA 2003-12-04 16:14:15 EST 
Since we are focusing on bug fixes for M6 I am moving this to M7
Comment 10 Darin Swanson CLA 2004-03-18 13:47:06 EST 
Nothing more planned for 3.0
Comment 11 Denis Roy CLA 2009-08-30 02:24:13 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.