Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4065454

Using javadoc to integrate new packages

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P5 P5
    • 1.2.0
    • 1.0.2, 1.1.1, 1.1.2, 1.1.4, 1.2.0
    • tools
    • 1.2rc1
    • generic, x86, sparc
    • generic, solaris_2.5.1, windows_nt

      Name: rlT66838 Date: 07/17/97
      I would like to have a unified (merged) set of html pages
      for the jdk api, third party packages and classes
      we develop in house, stored on our intranet for
      company-wide access. Using javadoc, I find that
      if I run the utility for a given set of packages,
      the resulting tree.html has no hyperlinks to the
      api classes, while packages.html and AllNames.html
      apply only to the classes found during this
      execution. While it is advantageous to segregate
      the api from third party package and in-house
      development (AllNames would become unwieldy !), it
      would be helpful to have some hyperlink connection
      from add-ons to the api, without having to
      manually change the summary pages. The most
      helpful change would be to have a switch for
      specifying the directory of the jdk api
      documentation, so that a third party or in-house
      set of packages could be in a sub-directory, and
      their specific tree.htm could have hyperlinks to
      the api classes.

      ======================================================================
      Keywords: merge, unify

            adambalksunw Atul Dambalkar (Inactive)
            rlewis Roger Lewis (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: