From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701
Description of problem:
In the CMS javadoc, references to Core classes should be links, the same way
they are for references to J2SE classes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. View CMS javadoc
Actual Results: References to Core classes are plain text, not links to Core
Expected Results: References should be links
This is now possible because javadoc accepts multiple -link options.
I've always wondered how the javadoc util decides which of the
multiple external URLs to use, when creating an href.
Turns out that
The -link option requires that a file named package-list, which is
generated by Javadoc, exist at the URL you specify with -link. The
package-list file is a simple text file that lists the names of
packages documented at that location.
For example, the package list for the Java 2 Platform v1.3 API is
starts out as follows:
Anyhow, the bottom line is, we have to jump through additional
hoops to make javadoc correctly resolve references to core classes.
Is this bug saying that CMS Javadoc in a development should link to
Core Javadoc from that same development environment (or machine), or
just that the canonical CMS Javadoc on rhea.redhat.com should link to
the canonical Core Javadoc on rhea.redhat.com?
The latter (canonical CMS Javadoc should link to canonical Core Javadoc).
The 6.1 javadoc is now live and cms links to core.
closing old tickets