Bugzilla – Full Text Bug Listing
| Summary: | Navigate to package | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Lukas Eder <lukas.eder> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert, stephan.herrmann |
| Version: | 4.5 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Hi Lukas, I guess, one option for creating the connection from Java editor to Package Explorer would be to say "Show in > Package Explorer". I was actually expecting this to work when invoked on the type name, but the "Show in" command doesn't resolve the type I'm referring to. It always uses the enclosing element within the current compilation unit. @Team, is there a deeper meaning behind this, or could this command be changed to mean "show declaration in package explorer", when invoked over a reference? (In reply to Stephan Herrmann from comment #1) > Hi Lukas, > > I guess, one option for creating the connection from Java editor to Package > Explorer would be to say "Show in > Package Explorer". I was actually > expecting this to work when invoked on the type name, but the "Show in" > command doesn't resolve the type I'm referring to. It always uses the > enclosing element within the current compilation unit. > > @Team, is there a deeper meaning behind this, or could this command be > changed to mean "show declaration in package explorer", when invoked over a > reference? For the Java editor, Show In reveals the same element as Link With Editor. I would not like to change that. Extending Ctrl+Click / F3 seems more natural. If you hover over the imports, you'll see an Open Declaration button, which does what's requested in comment 0. |
This would be a nice-to-have feature. When I Ctrl-Click or F3 on a package name of a package that is on the classpath, I'd like to go to the location in the Package Explorer view, where that package is declared, in order to introspect its contents. Optionally, if there is a package-info.java, then that file should be opened. An example: ---------------------------------------------------------------- import static java.util . Arrays.asList; // ^^^^ ^^^^ ^^^^^^ ^^^^^^ --- clicking on these already works // ||||-||||---------------------- clicking on these would be useful, too class Test { private java.util . Map m; // ^^^^ ^^^^ ^^^ --------------- clicking on this already works // ||||-||||------------------------ clicking on this would be useful, too } ---------------------------------------------------------------- I know it's not the same kind of action, because that action would be executed in a view, not in the editor - so my above description is probably not 100% consistent with general Eclipse behaviour. But I would still find the general idea very useful.