Doug Kramer wrote to the submitter:
> Thank you for submitting this bug. We need some more information.
> Are the classes HeartBeatBean and HeartBeatMgr (that are missing links)
> being passed into the javadoc command? That is, are they included
> in the JAVADOC_GROUPS_AND_PACKAGES environment variable?
Yes, they are being passed into the javadoc command, although not via
JAVADOC_GROUPS_AND_PACKAGES. They are being passed into the javadoc command
in the file $(TEMP_PCP_SOURCE_DIR)/workfile2. This file contains a list
of files that I wish to javadoc in addition to those listed in JAVADOC_GROUPS_AND_PACKAGES. One point to note is that javadoc is
creating javadoc documentation for HeartBeatBean and HeartBeatMgr.
The only problem is that the links are being displayed as text.
Yes, the classes HeartBeatBean and HeartBeatMgr are being passed into the javadoc command. They are included in the TEMP_PCP_SOURCE_DIR environment
variable... I also tried including the path to the source via the
-classpath entry, although this did not work either i.e. I included TEMP_PCP_SOURCE_DIR in the -classpath entry.
> If not passed in, are they referenced in any import or
> declaration statements?
Yes, they are being imported and used within the other classes.
> Are these two classes referenced in the body of any methods?
The methods used in my example should be returning objects of type
HeartBeatBean or HeartBeatMgr. I only used these two classes as examples.
The same problem is occurring for many other classes.
> Are the paths to those classes contained in -classpath or -sourcepath?
Any other questions, let me know.
In my opinnion, this bug is a duplicate of 4628281. This regression bug was introduced in merlin:
When you document a source file instead of a package (such as c:\foo\Bar.java), the classdoc that represents Bar will return false when method "isIncluded()" is called. This is why the user reports that links are missing from the output. I think this might be a bug in the javadoc tool. I have found a way to fix this in the standard doclet (using the new ClassDocCatalog), but this might not be the right solution. I will investigate this futher by doing some testing with the javadoc tool.