Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Mon, 7 Oct 2013 11:45:41 +0000 (UTC)
From: "Ate Douma (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12404476.1221611825718.24998.1381146341883@arcas>
In-Reply-To: <JIRA.12404476.1221611825718@arcas>
References: <JIRA.12404476.1221611825718@arcas>
Subject: [jira] [Commented] (COMMONSSITE-38) Upgrade to maven-javadoc-plugin
 2.5 / *-javadoc.jar Manifest entries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COMMONSSITE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788090#comment-13788090 ] 

Ate Douma commented on COMMONSSITE-38:
--------------------------------------

Isn't this one outdated or else done?

> Upgrade to maven-javadoc-plugin 2.5 / *-javadoc.jar Manifest entries
> --------------------------------------------------------------------
>
>                 Key: COMMONSSITE-38
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-38
>             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 was sent by Atlassian JIRA
(v6.1#6144)