Maven 1.x Javadoc Plugin

Default javadoc scope (package) can't be replaced by private or public

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6, 1.6.1
  • Fix Version/s: 1.7
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Because the plugin defines the three following properties

maven.javadoc.package = true
maven.javadoc.private = false
maven.javadoc.public = false

if the user set maven.javadoc.private = true or maven.javadoc.public = true then there'are two scopes defined at the same time and the javadoc fails.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
dion gillard added a comment -

maven.javadoc.package = false
maven.javadoc.private = true
maven.javadoc.public = false

Doesn't work?

Show
dion gillard added a comment - maven.javadoc.package = false maven.javadoc.private = true maven.javadoc.public = false Doesn't work?
Hide
Permalink
Arnaud Heritier added a comment -

Yes it works, but I don't find this very intuitive (and bad documented).
I prefer to remove the default values and the user can set only one property.

Show
Arnaud Heritier added a comment - Yes it works, but I don't find this very intuitive (and bad documented). I prefer to remove the default values and the user can set only one property.
Hide
Permalink
Arnaud Heritier added a comment -

Fixed

Show
Arnaud Heritier added a comment - Fixed

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.