This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ BUILD # : 201110030601 ] [ JDK VERSION : 1.6.27 ] Hi, in a Netbeans Platform Project (like the PaintApplication example) if I select the project and run Tool --> Analyze Javadoc, the analyzer windows opens but it is empty (see figure 1). If a select a module for the same application (for example the module Paint) and run "Analyze Javadoc" the Analyzer window contains all warnings. (see figure 2). If this is an intended behavior (i.e. the "Analyze Javadoc" cannot be run on Projects but only on single modules) the Analyze menu item should be not selectable when a project is selected. By the way the "Analyze javadoc" works on a standard (non Netbeans Platform) java project. Gualtiero
Created attachment 111525 [details] Figure 1: the analyzer window (empty) after run on NetBeans platform project
Created attachment 111526 [details] Figure 2: the analyzer window after run on simgle module
(In reply to comment #0) > If this is an intended behavior (i.e. the "Analyze Javadoc" cannot be run on > Projects but only on single modules) It is intended. The suite project has no Java sources so it cannot be analyzed. You must select projects containing Java sources, such as the NBM (module) projects. Probably you can multiselect all the module projects in a suite, though I cannot confirm - when I run Analyze Javadoc it is usually (but not always!) empty no matter what my selection is. Seems to be broken somehow. > the Analyze menu item should be not selectable when a [suite] is selected. Perhaps not.
>Probably you can multiselect all the module projects in a suite, though I cannot confirm - when I run Analyze Javadoc it is usually (but not always!) empty no matter what my selection is. Seems to be broken somehow. It is not broken. Javadoc is generated by default only for classes in public packages and most packages in module suites are not public. If you want to check also not-public packages, go to Options | Editor | Hints | Javadoc | Create Javadoc and check [x] Check also publicly unavailable packages Analyze javadoc works with multi-selection
So there probably remains a UI bug that if the analyzer is invoked on a project with no Java source roots (like the suite), or on a project with no public packages (like many modules), the Analyzer window should show a warning to this effect. (Or do not open the window at all but show an informational dialog.)
...and reopening for that.
no plans for fix