Closed GoogleCodeExporter closed 9 years ago
The proposed solution would be to add VM arguments section. The eclipse.ini
needs to go side-by-side with the main eclipse executable in the Eclipse.App
folder.
A possible (but not verified) workaround is to use Eclipse 3.0's old style of
running SWT applications:
- use java_swt to launch SWT based applications
(it is basically the same as "/usr/bin/java -XStartOnFirstThread")
- don't use the StartOnFirstThread command line option
- define the headless property
Because the StartOnFirstThread option is not defined, AWT should not complain
about running in the wrong thread.
Original comment by whatni...@gmail.com
on 31 Jan 2011 at 12:19
Original comment by vladimir...@gmail.com
on 18 May 2011 at 5:59
Original issue reported on code.google.com by
robert.w...@gmail.com
on 13 Mar 2010 at 3:01