Uploaded image for project: 'Gradle'
  1. Gradle
  2. GRADLE-378

Gradle's javadoc task should provide more propreties that allow for finer-grained tuning of Javadoc

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.6

      Description

      The current level of tuning offered by Gradle's javadoc task is inadequate.
      While it would be nice if every feature were supported, most users expect
      the most commonly used features of Javadoc to be available.

      Some properties are inherently problematic, like "private" (which is a Groovy keyword),
      and some require more back & forth between the underlying Ant.javadoc object than
      is convenient w/o the use of properties devoted to passing closures (which might be cool
      but might also represent a bit of work to get the interface just right). Still there's a lot of
      "low hanging fruit" – commonly needed stuff that's easy to implement.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              teyckmans Tom Eyckmans
              Reporter:
              jcox Jon Cox
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: