Community
Participate
Working Groups
java.lang.NullPointerException at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.deleteConflictingProjects(PluginImportOperation.java:189) at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.runInWorkspace(PluginImportOperation.java:129) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
It seems to happenned when you have already the plugin in your workspace in the state closed
This is working fine for me in 3.7 and in 3.6.1. The plug-in model manager should not ever be returning a null plug-in. I don't see anywhere in the code that has changed that would affect this.
Hum, I tried with a fresh elipse installed and it effectively works nicely. I reproduce it in my Eclipse used for my development. I will try to investigate a little more to determine what is the reason.
(In reply to comment #3) > Hum, I tried with a fresh elipse installed and it effectively works nicely. > > I reproduce it in my Eclipse used for my development. > I will try to investigate a little more to determine what is the reason. You'll need to be pointing to a target definition (that isn't the current target platform) that ends up having an error during the target resolve. This can probably be reproduced by creating a target that has a bundle with a mangled manifest file.
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.
This bug has been marked as stalebug a while ago without any further interaction. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
