| Summary: | Scrapbook page does not see reexported plugins | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Nick Edgar <n.a.edgar> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | stalebug | ||
|
Description
Nick Edgar
Deferred. Code completion in the snippet editor is based on its project and explicit imports. Currently, you only get the imports from the current project for free. Not sure if all packages on classpath should be added as imports for free or not. Note that I wasn't expecting it to automatically import everything. I just expected the type to be visible. When I said "expecting it to complete to DialogSettings in JFace" I meant the fully qualifed path: org.eclipse.jface.dialogs.DialogSettings. Although it would be a nice enhancement for it to offer to add it as an import to the page. But the main problem here is that the type just wasn't visible without explicitly adding JFace to the project's build path. Re-opening for investigation. May be a JCORE bug. When I create a scrapbook page in a plug-in projet that has org.eclipse.ui as a required plug-in I can see DialogSettings for free when code assisting in the scrapbook page. When I create a scrapbook page in a plain Java project and add org.eclipse.ui as a required project, I cannot see DialogSettings (re- exported plug-ins) for free. Moving to JCORE for comment. It could be that plain Java projects do not inherit re-exported plug-ins from required projects that happen to be plug-ins. In my case the scrapbook page was in a plain Java project. 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. |