Community
Participate
Working Groups
Created attachment 169958 [details] Screenshot of result I20100523-0800 Import binary plug-ins, existing unshared, confirm replacement. A few plug-ins have been imported correctly, but at org.apache.lucene, it stopped with an NPE and left the workspace screwed, see screenshot (all the other projects for binary plug-ins are closed). Error Wed May 26 11:17:02 CEST 2010 An internal error occurred during: "Import Plug-ins and Fragments". java.lang.NullPointerException at java.io.File.<init>(File.java:222) at org.eclipse.pde.internal.core.PDERegistryStrategy.getFile(PDERegistryStrategy.java:238) at org.eclipse.pde.internal.core.PDERegistryStrategy.addBundle(PDERegistryStrategy.java:183) at org.eclipse.pde.internal.core.PDERegistryStrategy.addBundles(PDERegistryStrategy.java:173) at org.eclipse.pde.internal.core.PDERegistryStrategy.processBundles(PDERegistryStrategy.java:168) at org.eclipse.pde.internal.core.PDERegistryStrategy.onStart(PDERegistryStrategy.java:148) at org.eclipse.core.internal.registry.ExtensionRegistry.<init>(ExtensionRegistry.java:725) at org.eclipse.core.runtime.RegistryFactory.createRegistry(RegistryFactory.java:58) at org.eclipse.pde.internal.core.PDEExtensionRegistry.createRegistry(PDEExtensionRegistry.java:85) at org.eclipse.pde.internal.core.PDEExtensionRegistry.getRegistry(PDEExtensionRegistry.java:77) at org.eclipse.pde.internal.core.PDEExtensionRegistry.getExtensionPoint(PDEExtensionRegistry.java:134) at org.eclipse.pde.internal.core.PDEExtensionRegistry.findExtensions(PDEExtensionRegistry.java:205) at org.eclipse.pde.internal.core.SourceLocationManager.processExtensions(SourceLocationManager.java:342) at org.eclipse.pde.internal.core.SourceLocationManager.getExtensionLocations(SourceLocationManager.java:192) at org.eclipse.pde.internal.core.SourceLocationManager.searchExtensionLocations(SourceLocationManager.java:273) at org.eclipse.pde.internal.core.SourceLocationManager.findSourcePath(SourceLocationManager.java:60) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.getSourceManager(PluginImportOperation.java:701) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importSourceArchives(PluginImportOperation.java:769) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importAsBinary(PluginImportOperation.java:375) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importPlugin(PluginImportOperation.java:337) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.runInWorkspace(PluginImportOperation.java:147) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>and left the workspace screwed, See bug 313489 comment 6.
After I've deleted the broken org.apache.lucene project, the PDE wizard could import that bundle again. But for all the closed projects, I still have to import the plug-ins manually.
I got this same NPE while debugging bug 314706 java.lang.NullPointerException at java.io.File.<init>(File.java:222) at org.eclipse.pde.internal.core.PDERegistryStrategy.getFile(PDERegistryStrategy.java:238) at org.eclipse.pde.internal.core.PDERegistryStrategy.addBundle(PDERegistryStrategy.java:183) at org.eclipse.pde.internal.core.PDERegistryStrategy.addBundles(PDERegistryStrategy.java:173) at org.eclipse.pde.internal.core.PDERegistryStrategy.processBundles(PDERegistryStrategy.java:168) at org.eclipse.pde.internal.core.PDERegistryStrategy.onStart(PDERegistryStrategy.java:148) at org.eclipse.core.internal.registry.ExtensionRegistry.<init>(ExtensionRegistry.java:725) at org.eclipse.core.runtime.RegistryFactory.createRegistry(RegistryFactory.java:58) at org.eclipse.pde.internal.core.PDEExtensionRegistry.createRegistry(PDEExtensionRegistry.java:85) at org.eclipse.pde.internal.core.PDEExtensionRegistry.getRegistry(PDEExtensionRegistry.java:77) at org.eclipse.pde.internal.core.PDEExtensionRegistry.getExtensionPoint(PDEExtensionRegistry.java:134) at org.eclipse.pde.internal.core.PDEExtensionRegistry.findExtensions(PDEExtensionRegistry.java:205) at org.eclipse.pde.internal.core.SourceLocationManager.processExtensions(SourceLocationManager.java:342) at org.eclipse.pde.internal.core.SourceLocationManager.getExtensionLocations(SourceLocationManager.java:192) at org.eclipse.pde.internal.core.SourceLocationManager.searchExtensionLocations(SourceLocationManager.java:273) at org.eclipse.pde.internal.core.SourceLocationManager.findSourcePath(SourceLocationManager.java:60) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.getSourceManager(PluginImportOperation.java:701) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importSourceArchives(PluginImportOperation.java:769) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importAsBinary(PluginImportOperation.java:375) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.importPlugin(PluginImportOperation.java:337) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.runInWorkspace(PluginImportOperation.java:147) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
(In reply to comment #3) > I got this same NPE while debugging bug 314706 Me too, after I started I20100526-1625 with the patch for bug 314706.
(In reply to comment #4) > (In reply to comment #3) > > I got this same NPE while debugging bug 314706 > Me too, after I started I20100526-1625 with the patch for bug 314706. FYI, on my second, third, etc., imports I did not get the NPE.
> FYI, on my second, third, etc., imports I did not get the NPE. Same here. I just updated to I20100527-0800 + patch from bug 314706, and both importing and compiling went well (several times).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
