| Summary: | [CommonNavigator] JDT refatoring actions appearing when they shouldn't | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jon Corchis <jcorchis> |
| Component: | UI | Assignee: | Michael D. Elder <mdelder> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | CC: | daniel_megert, dmisic, markus.kell.r, Mike_Wilson |
| Version: | 3.2 | ||
| Target Milestone: | 3.2 RC4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Jon Corchis
Jon, what elements are you talking about? Michael, can we do something here? EObjects that are wrapped in container objects that my content/action providers specifically target, so as to avoid overlap with other content/action providers. Ping. Michael, any update on this one? I'll need to follow up with Jon for a specific use case. The J2EE models in WTP also use EObjects in the viewer, and the JDT actions do not show up for those. I need more detail here before I can debug this issue. Can a use case be provided? EObjects alone are not enough to cause a problem as the J2EE extensions use EObjects for their content. What is different about the use case here? I have retested this (using the same environment as Jon had) with RC1a and I cannot reproduce this issue anymore. The only 'duplication' that I can see is for refactoring (Rename, Move) of resources - there are entries that I am guessing are coming from platform plus another set of entries we set up for our resources. I guess we should refactor our resource refactoring code :) to provide participants instead of doing everything? Either way, that is not a topic of this Bugzilla and I think this bug could be marked as fixed. Closing as Invalid as the defect is no longer relevant or reproducible. The duplications showing up on resources are definitly coming from JDT. I have logged a separate Buzilla to track this (Bug 141151). . |