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

Bug 286043

Summary:	Mac system.log Unrecognized Java VM option ignored
Product:	[Eclipse Project] Platform	Reporter:	Dan <dentous>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	aniefer
Version:	4.0
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Dan

2009-08-08 02:20:23 EDT

Build ID: 20090619-0625

Steps To Reproduce:
1. Open Eclipse
2. View the Mac /private/var/log/system.log

More information:
I installed Eclipse for PHP Developers - I couldn't find that in the plugin/component list so I selected the Platform - hope that was correct.

Found this thread, http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg03742.html, but could not find the bug report id or resolution.

Mac OS X 10.5.8

Comment 1 Dan

2009-08-08 02:21:51 EDT

Aug  8 08:16:05 noname /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse[396]: Unrecognized Java VM option ignored: -XstartOnFirstThread
Aug  8 08:16:05 noname /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse[396]: Unrecognized Java VM option ignored: -Xdock:icon=../Resources/Eclipse.icns
Aug  8 08:16:05 noname /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse[396]: Unrecognized Java VM option ignored: -XstartOnFirstThread

Comment 2 Prakash Rangaraj

2009-08-11 00:34:54 EDT

I'm getting similar errors in the log for RCP package as well. AFAIK, they are valid VM arguments. Does Apple changed something in JDK 6/Cocoa? Assigning to SWT for comments

Comment 3 Kevin Barnes

2009-08-11 09:29:41 EDT

Andrew - do you know why these messages are being logged?

Comment 4 Andrew Niefer

2009-08-11 10:13:46 EDT

These arguments are consumed by the java executable launcher, not by the jvm itself.  When using the eclipse launcher, the java launcher is not involved and we go directly to the jvm through the JNI invocation API.

*** This bug has been marked as a duplicate of bug 209722 ***