| Summary: | NPE in PluginManifestChange.createRenameChange(..) while renaming/moving/refactoring | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Andrey Zavtrakov <andrey> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | markus.kell.r, remy.suen, Vikas.Chandra |
| Version: | 3.6.1 | Keywords: | investigate |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
Andrey Zavtrakov
Possibly caused by a corrupt extension point trying to participate in the refactoring. can i do something to find this corrupted extension? The problem is somewhere around PluginManifestChange.createRenameChange(PluginManifestChange.java:64), see the root exception in comment 0. The API IPluginExtension#getPoint() promises to return an ID, but both implementations can return null in some cases. 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 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 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. |