|
Re: Workbench not persisted under Mac [message #1407846 is a reply to message #1407727] |
Wed, 13 August 2014 15:46 |
Eclipse User |
|
|
|
There are no special settings required for the Mac. Look at your <product>.ini file and the configuration/config.ini and verify that the arguments and settings are what you expect. And look at your .product definition file to ensure you haven't set some platform-specific settings there.
We'll need more detail (e.g., configuration information above, plus about the IllegalSateException from -data). But before you do, try using the Eclipse 4 Model Editor (which includes the Eclipse 4 Tools) to create a dummy application (Eclipse 4 > Eclipse 4 Application Project) and verify that it doesn't work either.
Note: The directory should be org.eclipse.e4.workbench, not .ui.workbench.
Brian.
|
|
|
|
|
|
|
Re: Workbench not persisted under Mac [message #1408674 is a reply to message #1408534] |
Fri, 15 August 2014 19:02 |
Eclipse User |
|
|
|
Marina Knieling wrote on Fri, 15 August 2014 05:51
a colleague found out that setting -DpersistState=true in the product
file in the VM arguments works. This flag seems to default to true under
Windows but not under Mac. Not setting -persistState (in the normal way)
persists the workbench under Windows anyways, but not under Mac.
-persistState takes an argument, true or false. That you're not providing one means that the behaviour is undefined, and likely false. See the code in E4Application#loadApplicationModel() around line 389:
// Save and restore
boolean saveAndRestore;
String value = getArgValue(IWorkbench.PERSIST_STATE, appContext, false);
saveAndRestore = value == null || Boolean.parseBoolean(value);
I don't know why your model was persisting under Windows -- that's more of a bug!
Brian.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03821 seconds