Bug 104419 - Don't issue missing doc warning for hidden members
Summary: Don't issue missing doc warning for hidden members
Status: RESOLVED DUPLICATE of bug 86769
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-19 17:41 EDT by Jens Elkner CLA
Modified: 2005-07-25 14:28 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Elkner CLA 2005-07-19 17:41:25 EDT
If javadoc warnings for the scope protected and above are enabled, there should
be  no missing comment warnings for any members of a member with a visibility
less than protected.

E.g. 

public class A {
  private class Bla extends AbstractAction {
    public void actionPerformed(ActionEvent e) {
      ...
    }
  }
}

There should be no "missing javadoc" warning, since the whole class will never
get into the javadoc because of private visibility... So pretty sensless to
issue a warning and especially if one uses a lot of inner/anonymous classes this
is more than annoying. And because of the bunch of warnings I've seen a lot of
people starting to ignore/filter out or even disable those warnings. And thus
finally makes the complete warning system superfluous or at least to degrade its
usage to not production ready ...
Comment 1 Markus Keller CLA 2005-07-20 06:54:51 EDT
Moving to JDT/Core. 
Comment 2 Frederic Fusier CLA 2005-07-25 02:44:47 EDT

*** This bug has been marked as a duplicate of 86769 ***
Comment 3 Jens Elkner CLA 2005-07-25 11:53:21 EDT
It might be a duplicate, but 86769  has been marked as resolved, which isn't
true ...
Comment 4 Frederic Fusier CLA 2005-07-25 14:28:57 EDT
It's *really* a duplicate.
Bug 86769 was marked as RESOLVED but status was LATER. That means bugs is NOT
resolved but will be fixed later...
This is the way bugzilla works. If you think this behavior is not good, please
open a requirement against it...


*** This bug has been marked as a duplicate of 86769 ***