Community
Participate
Working Groups
When PDE generates an application for Mac OS X it's adding the lines "-XstartOnFirstThread" and "-Xdock:<path to icon>" to the application's .ini file. This is unnecessary and leads to problems like bug 320089. The -X arguments are only understood by the java command-line tool and are removed from the arguments passed to JVM via JNI. (I know this, because I wrote the support for them when I was at Apple!) This information is already specified in other ways because Eclipse and other RCP applications are bundled applications. The Eclipse launcher already knows to start the JVM on thread 0 on Mac OS X, and in a bundled Mac application the name of icon is specified in <name>.app/Contents/Info.plist. To the best of my knowledge you can't start an RCP app from the command line, but even if you could, these arguments shouldn't be passed into the JVM.
Sending this to UI for now, the .product files are created with "-XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts" as default vm args for mac. I'm not sure where the -Xdock is coming from
I can't find anywhere in PDE that we add or edit -Xdock.
We have now seen this happen on the mac. The argument is coming from your target platform. The default target platform gets a list of arguments from the current install. So if your running Eclipse has -XDock in its config.ini, it will be added to new launch configs by default. If you don't want these arguments, you can remove them on the target platform preference page. Just open the current target platform, go to the arguments tab, and remove the arguments you don't want.
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.
