Community
Participate
Working Groups
The following problem was reported via the automated error reporting: Message: Failed to restart Eclipse. The Eclipse VM arguments could not be read. org.eclipse.recommenders.utils.Logs$LogTraceException: null at org.eclipse.recommenders.internal.rcp.BundleResolutionFailureDialog.buildCommandLine(BundleResolutionFailureDialog.java:156) at org.eclipse.recommenders.internal.rcp.BundleResolutionFailureDialog.buttonPressed(BundleResolutionFailureDialog.java:131) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) Bundles: | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | | org.eclipse.recommenders.rcp | 2.3.0.v20160216-1255 | 2.3.0.v20160216-1255 | | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | Operating Systems: | Windows | 10.0.0 | 10.0.0 | The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/577117c5e4b0e5ad9127c409 for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. Created on behalf of andreas.sewe@xxxxxx.xxx
I cannot reproduce this. Under Windows 10, using the "Platform Runtime Binary" from [1] (product ID org.eclipse.platform.ide, version 4.5.2.M20160212-1500) I have the eclipse.vm system property set, which BundleResolutionFailureDialog.buildCommandLine complains about being null. If this error occurs again, can you please attach your About Eclipse > Installation Details > Configuration to this bug. Thank you. [1] <http://download.eclipse.org/eclipse/downloads/drops4/R-4.5.2-201602121500/>