Community
Participate
Working Groups
Build Identifier: 20110916-0149 When a class has no constructor in its source code, its implicit constructor should be visible in the Package Explorer, Project Explorer, and Outline views so that 1. the developer is aware of the constructor, 2. the developer can set an entry breakpoint to the constructor, 3. the developer can search for references to the constructor, including explicit or implicit super() calls from subclasses. Reproducible: Always Steps to Reproduce: Write a class as simple as public class C { } and observe that its constructor is not visible in the outlines.
The outline view shows elements explicitly defined in the java file in the editor. (In reply to comment #0) > 1. the developer is aware of the constructor A java developer will anyway be aware of the c'tor. > 2. the developer can set an entry breakpoint to the constructor, And do what? How do we show the action of the object being constructed in the debug perspective? There's nothing in the editor. > 3. the developer can search for references to the constructor, including > explicit or implicit super() calls from subclasses. That can still be done. Go to Java search, type the class name, select 'search for' - constructor, and 'limit to' - references. This should suffice. Anyway, moving to JDT/UI for the decision.
The Outline view shows what's in the Java model which doesn't contain the default constructor in case of Java source files. This is correct and won't be changed. *** This bug has been marked as a duplicate of bug 37382 ***
Verified for 3.8 M6
(In reply to comment #1) > 2. the developer can set an entry breakpoint to the constructor, > And do what? Even if there is no source code line to point at, the developer would be able to inspect the process stack in the Debug view to see the context the constructor was called from.
