maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Commented] (MJAVADOC-560) Clarify outputDirectory, reportOutputDirectory in javadoc:javadoc documentation
Date Sun, 10 Feb 2019 17:52:00 GMT


Robert Scholte commented on MJAVADOC-560:

Indeed, javadoc:javadoc should not have a reference to outputDirectory. Not sure when it was
introduced, but maybe due to the combinations of reports, jars and aggregators this was hard
to solve.

> Clarify outputDirectory, reportOutputDirectory in javadoc:javadoc documentation
> -------------------------------------------------------------------------------
>                 Key: MJAVADOC-560
>                 URL:
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>          Components: javadoc
>    Affects Versions: 3.1.0
>            Reporter: Gili
>            Priority: Major
> Looking at the documentation for javadoc:javadoc at [] I
see three problems:
>  # The documentation lists both *outputDirectory* and *reportOutputDirectory* parameters,
having the same description. It's not clear what each one is used for or what happens if one
property is changed without the other.
>  # The default value of *outputDirectory* is listed as *${}/apidocs*
but the value that is actually used is *${project.reporting.outputDirectory}/apidocs* (the
value of *reportOutputDirectory*).
>  # It was extremely difficult to find any documentation on *${project.reporting.outputDirectory}***,
such as what its default value is. I eventually found [] but
Google does not link directly to this page/section because it doesn't contain an explicit
reference to *${project.reporting}*.
> Suggested fix(es):
>  # Drop one of the two parameters, ideally *reportOutputDirectory*, to avoid confusion.
>  # Update the documentation so it lists the correct default value for *outputDirectory*.
>  # Link directly from mention of *${project.reporting.outputDirectory}* to []

This message was sent by Atlassian JIRA

View raw message