|
|
|
Re: Relaunching Eclipse RCP Application [message #1415856 is a reply to message #756892] |
Wed, 03 September 2014 20:50 |
Darrel Karisch Messages: 14 Registered: July 2012 |
Junior Member |
|
|
Is there a resolution to this problem?
I'm using Kepler 4.3.2, the debugger is using the launcher org.eclipse.equinox.launcher.Main.
Yet, returning EXIT_RELAUNCH from an IApplication implementation does not relaunch.
eclipse.commands System property is:
-launcher\nC:\\ws\\.metadata\\.plugins\\org.eclipse.pde.core\\.bundle_pool\\eclipse.exe\n
-name\nEclipse\n
-showsplash\n600\n
-product\ncom.xxx.yyy.product\n
-configuration\nfile:C:/APPBASE/.metadata/.plugins/org.eclipse.pde.core/com.lgc.dsp.base.product/\n
-dev\nfile:C:/ws/.metadata/.plugins/org.eclipse.pde.core/com.xxx.yyy.product/dev.properties\n
-os\nwin32\n
-ws\nwin32\n
-arch\nx86_64\n
-nl\nen_US\n
-consoleLog\n
...
Adding "-exitdata arbitrary_value" argument to Debug Configuration Arguments does not help EXIT_RELAUNCH to relaunch the app.
However, it does provoke org.eclipse.equinox.launcher.Main::setExitData to pass exitdata along to JNIBridge::setExitData rather than merely printing out exitdata and exiting.
[Updated on: Thu, 04 September 2014 18:04] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.02642 seconds