Uploaded image for project: 'Groovy'
  1. Groovy
  2. GROOVY-5940

groovydoc does not show class hierarchy correctly

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.8.6, 2.0.6
    • 1.8.9, 2.0.7, 2.1.1, 2.2.0-beta-1
    • GroovyDoc
    • None
    • Win7 64bit

    Description

      Attachment bug1.zip contains 2 groovy projects ("foo" and "bar") plus an ant project (under folder "ant") to perform the groovydoc. I've tried groovydoc by:

      • running "ant" in the "ant" folder (I used apache-ant-1.8.4)
      • running "build.xml" as an Ant Build in eclipse (I used juno-4.2)
        The documentation is written to the folder "doc". I used "ant" for the attachment version.

      The build.xml copies the groovy files to a separate folder before invoking groovydoc. AFAICS this makes no difference to this problem - I get the same if I direct groovydoc to use the groovy files in their project folders.

      Class bar.Deriv is defined like this:

      bar.Deriv.groovy
      package bar
      class Deriv extends Base {
      }
      

      The page for bar.Deriv (doc/bar/Deriv.html) shows the hierarchy as:

      java.lang.Object
        foo.Base
            bar.Deriv
      

      However, bar.Deriv derives from bar.Base, not foo.Base.

      If you create the documentation yourself and find that groovydoc gets the hierarchy correct for bar.Deriv, try looking at the page for foo.Deriv (doc/foo/Deriv.html). It will get that one wrong instead.

      I think this is wrong: groovydoc should be able to resolve the base class to the correct package.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            asteingress Andre Steingress
            marshals simon misys
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment