Bug 68160 - Cannot use 'eclipse' command line launcher to launch eclipse app when no workspace specified on the command line
Summary: Cannot use 'eclipse' command line launcher to launch eclipse app when no work...
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Andre Weinand CLA
QA Contact:
URL:
Whiteboard:
Keywords: readme
Depends on:
Blocks:
 
Reported: 2004-06-22 10:14 EDT by Alex Blewitt CLA
Modified: 2004-06-22 19:38 EDT (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 Alex Blewitt CLA 2004-06-22 10:14:23 EDT 
This probably shouldn't be seen as an Eclipse 3.0 blocker; the Eclipse launcher stuff for Mac OS X is in 
need of attention anyway, and probably won't be resolved by Eclipse 3.0's final release.

I tried to launch 'eclipse' using the command line (as opposed to launching with the Eclipse.app icon), 
typing in: 
/tmp/eclipse/eclipse

This brought up the splash screen (as expected) and displayed a dialog asking for the default 
workspace location (since there was no -workspace on the command line.)

However, since the 'Eclipse.app' has in its Info.plist 'LSUIElement=1', the Mac window manager believes 
that that app shouldn't be capable of receiving user input; as such, the dialog, though visible, cannot be 
selected; thus, Eclipse is effectively hung.

The only solution would be to remove the LSUIElement=1 from the Info.plist; this should then enable 
user input.

I believe that the 'eclipse' command line launcher causes problems for the Mac .app in general; there 
are still outstanding bugs with the Mac .app in any case (e.g. Eclipse is shown in the dock as java_swt; it 
can't be docked, etc.) This bug is a further symptom of these sorts of Mac-specific issues.

Eclipse RC3 on Mac OS X.3.4
Comment 1 Andre Weinand CLA 2004-06-22 13:16:28 EDT 
The symbolic link works fine if you pass the correct vm to eclipse.
Try this:
./eclipse -vm /tmp/eclipse/Eclipse.app/Contents/MacOS/java_swt

The property LSUIElement=1 is not a problem since eclipse isn't using that section of the Info.plist file.

Yes, we could have made java_swt the default vm for "eclipse.exe".
But we still have hopes that java_swt will become obsolete...

This info will be part of the readme.
Comment 2 Andre Weinand CLA 2004-06-22 19:38:30 EDT 
Wrote readme entry and set to Jeem.