Community
Participate
Working Groups
build f2: I created the default eclipse self hosting run configuration and have been running with it for a while. this morning after trying again an error is shown that an internal exception has occured and the following was in the log: note: i can't launch anymore, i'm really stuck! java.lang.NullPointerException at java.util.Hashtable.put(Unknown Source) at java.util.Properties.setProperty(Unknown Source) at org.eclipse.pde.internal.ui.TargetPlatform.createPropertiesFile(TargetPlatform.java:105) at org.eclipse.pde.internal.ui.launcher.WorkbenchLaunchConfigurationDelegate.doLaunch(WorkbenchLaunchConfigurationDelegate.java:158) at org.eclipse.pde.internal.ui.launcher.WorkbenchLaunchConfigurationDelegate.launch(WorkbenchLaunchConfigurationDelegate.java:75) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:136) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog$10.run(LaunchConfigurationDialog.java:2279) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:98)
Check the configuration by calling 'Run...' and switch to the plugins and fragments tab. If you see any of the plug-ins with an error overlay, check if the plugin.xml or fragment.xml for that plug-ins has errors. You probably do not have PDE perspective associated with your projects, otherwise PDE builder would flag errors and create markers in the task list.
Fixed. I am 99% sure that you have broken plug-ins (i.e. syntax errors in plugin.xml or fragment.xml). To catch this earlier, consider attaching PDE nature to your projects - this will cause PDE builder to run and flag syntax errors in plugin manifests the usual way (in the task list). PDE will not flag broken plug-ins during the launch (but will allow you to continue with it). Note that launching with errors in the manifest files will cause those plug-ins to be disabled by the run-time workbench instance.
