Community
Participate
Working Groups
The Javadoc hover and the class file editor for classes without source should tell about the difference between JDK and JRE and help the user install and configure a JDK. Too often, I see people working against a JRE where they miss important tooling like the Quick Type Hierarchy and even Javadoc hovers if they are offline.
(In reply to comment #0) > Too often, I see people working against a JRE where they miss important > tooling like the Quick Type Hierarchy Why would the Quick Type hierarchy not work with a JRE?
> Why would the Quick Type hierarchy not work with a JRE? It only works on existing references to a type/member. It doesn't work in the class file editor without source.
(In reply to comment #2) > > Why would the Quick Type hierarchy not work with a JRE? > > It only works on existing references to a type/member. It doesn't work in the > class file editor without source. Yes, of course - like most other things that are source based. Also, being on- or offline has not influence on the Class File Editor.
This bug is just about a common story where we're not as helpful as we could be. Of course, a five-line story description can't go into details, but you should get the point if you care. (In reply to comment #3) I don't see the point in full-citing the previous comment. > Also, being on- or offline has not influence on the Class File Editor. Correct, but I didn't claim that. However, the Class File Editor is where people end up when they Ctrl+click or press F3, e.g. because they didn't see Javadoc when hovering over a reference because they were offline.
(In reply to comment #4) > This bug is just about a common story where we're not as helpful as we could > be. Don't get me wrong - I do see the usefulness of this feature ;-).
(In reply to comment #0) > The Javadoc hover and the class file editor for classes without source should > tell about the difference between JDK and JRE and help the user install and > configure a JDK. +1. Too many people ask about missing javadoc and attached javadoc etc. A simple hint about using a JDK (which really is the best solution here), would be nice.