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.

Bug 34368 - Javadoc is incorrect when package is shared between modules
Summary: Javadoc is incorrect when package is shared between modules
Status: VERIFIED FIXED
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: rbalada
URL: http://www.netbeans.org/download/dev/...
Keywords: JDK_SPECIFIC
Depends on:
Blocks:
 
Reported: 2003-06-13 08:55 UTC by David Konecny
Modified: 2003-12-11 14:24 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Konecny 2003-06-13 08:55:43 UTC 
JavaDoc for module core/registry published on
website
<http://www.netbeans.org/download/dev/javadoc/UnsupportedAPIs/RegistryOverFSAPI/index.html>
is incorrect. It contain classes from
openide/registry module. It is probably caused by
the fact that these two modules uses both the same
package "org.netbeans.api.registry".

The core/registry has only one public class
FileSystemContextFactory. If you build JavaDoc for
this module from command line everything is fine.
Comment 1 David Konecny 2003-06-23 13:05:56 UTC 
I had to rename the package and it seems to fixed also this problem.
Comment 2 Jaroslav Tulach 2003-06-30 17:00:49 UTC 
Jesse told me that this is a problem in JDK's javadoc implementation
and that it has been fixed in 1.4.2. And I can confirm that on my
local computer when using 1.4.2 everything works fine. 

Ruda, please switch the javadoc build to use JDK 1.4.2.
Comment 3 Jesse Glick 2003-06-30 18:16:16 UTC 
Agreed. JDK 1.4.2 was recently released, so there should not be
objections to using a beta or internal build in the build process. The
main build of the product could stay using 1.4.0 for safety (to make
sure that we do not accidentally use any methods introduced after
1.4.0, if there are any), while switching the JDK version used for the
Javadoc build to 1.4.2.

1.4.0 has some problems in Javadoc. (For example, this one - when
running Javadoc on a set of sources in a package, if the classpath
contains other (sourceless) public classes in the same package, bogus
HTML summaries will be generated for them too.) 1.4.1 has a *lot* of
problems and should not be used. But so far, 1.4.2 seems pretty good
as far as stability of Javadoc goes.
Comment 4 rbalada 2003-08-18 09:20:54 UTC 
JDK 1.4.2 has been recently employed in javadoc generation.
Would you please check, whether this issue is still valid or fixed?
Comment 5 David Konecny 2003-08-18 09:36:50 UTC 
I cannot. I do not have any module with conflicting packages anymore.
I renamed it.
Comment 6 rbalada 2003-08-18 13:17:58 UTC 
Reopen if this issue reappears.
Comment 7 Jesse Glick 2003-08-18 13:40:44 UTC 
At least the problem with "ghost" classes seems to be fixed for the
dev Javadoc build. Compare:

http://www.netbeans.org/download/release35/javadoc/CompilerAPI/org/openide/loaders/package-summary.html

vs.

http://www.netbeans.org/download/dev/javadoc/CompilerAPI/org/openide/loaders/package-summary.html