Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 288408

Summary: [launcher] .ee file can force Mac to fork the jre, but it will fail
Product: [Eclipse Project] Equinox Reporter: Andrew Niefer <aniefer>
Component: LauncherAssignee: Project Inbox <equinox.launcher-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard: stalebug

Description Andrew Niefer CLA 2009-09-02 16:35:42 EDT 
The .ee file can be used to have the launcher fork the vm in a new process.

On the Mac, we always use JNI, but that restriction doesn't cover the .ee file.  So a .ee file can be used to make the Mac attempt to fork the vm.

However, the Mac implementation of vm forking doesn't exist, and just returns -1.

We need to either implement the vm forking, or force JNI in this case.

Bug 276763 indicates there may be some desire in the community for allowing the fork.
Comment 1 Eclipse Genie CLA 2019-03-08 15:22:14 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Lars Vogel CLA 2019-10-08 10:45:19 EDT 
This bug was marked as stalebug a while ago. Marking as wontfix.

If this report is still relevant for the current release, please
reopen and remove the stalebug whiteboard tag.