| Summary: | NPE when viewing local history | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Michael Giroux <michael_giroux> | ||||
| Component: | Team | Assignee: | Platform Team Inbox <platform-team-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | daniel_megert | ||||
| Version: | 3.5 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Michael Giroux
Are these modules new resources (not yet committed, marked with "?") in a SVN shared project? (In reply to comment #1) > Are these modules new resources (not yet committed, marked with "?") in a SVN > shared project? Yes. (In reply to comment #1) > Are these modules new resources (not yet committed, marked with "?") in a SVN > shared project? BTW, the NPE does not occur on every one of these resources. There are a few that display a message box indicating there is no local history. When you switch to History view for one of the modules and press Shift+Alt+F1, what does Plug-in Spy you just opened say about active view class and contributing plug-in? Created attachment 174914 [details]
Shift-Alt-F1 screenshot
A screenshot of the Shift-Alt-F1 from history view.
Is it possible that you will export the project, so I can reproduce the bug on my side? You don't have to include all the files, just make sure the one causing trouble is there. (In reply to comment #6) > Is it possible that you will export the project, so I can reproduce the bug on > my side? You don't have to include all the files, just make sure the one > causing trouble is there. Sorry, I had to commit the code to SVN, and now, the problem no longer exists. If I see it again I will be sure to save the project for you. Michael 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. |