commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] Commented: (COMMONSSITE-38) Upgrade to maven-javadoc-plugin 2.5 / *-javadoc.jar Manifest entries
Date Tue, 12 May 2009 00:46:46 GMT


Sebb commented on COMMONSSITE-38:

The javadoc plugin sections look a bit odd when compared with most other plugins.

The pluginManagement section has the version and a partial configuration.
The reporting section repeats the version and provides a fuller configuration.

Surely the version should only be provided in the pluginManagement section?
I don't think it works in the report section anyway, but it is confusing to have two instances.

Also the actual configuration should surely be confined to the reporting section?

> Upgrade to maven-javadoc-plugin 2.5 / *-javadoc.jar Manifest entries
> --------------------------------------------------------------------
>                 Key: COMMONSSITE-38
>                 URL:
>             Project: Commons All
>          Issue Type: Improvement
>          Components: Commons Parent Pom
>            Reporter: Niall Pemberton
>            Priority: Minor
>         Attachments: COMMONSSITE-38-javadoc-jar-manifest.patch
> The recent release of version 2.5 of the maven-javadoc-plugin now provides for the ability
to configure manifest entries in the same way as the maven-jar-plugin does.
> We can add this to commons-parent - the only thing I noticed is that it requires maven
2.0.9 as the minimum. Tried it out and it looks OK. The other thing is do we want to differentiate
from the jar manifets (perhaps add JavaDoc to titles).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message