maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MJAVADOC-431) allow javadoc jar to contain Maven descriptor
Date Tue, 01 Dec 2015 15:47:11 GMT


ASF GitHub Bot commented on MJAVADOC-431:

GitHub user peterlynch opened a pull request:

    MJAVADOC-431 allow maven descriptor to javadoc jar


You can merge this pull request into a Git repository by running:

    $ git pull MJAVADOC-431-maven-descriptor-2

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #70
commit d9b32cbbde1d617832211b712f6ea81e4a5de0fe
Author: Peter Lynch <>
Date:   2015-12-01T15:44:36Z

    MJAVADOC-431 allow maven descriptor to javadoc jar


> allow javadoc jar to contain Maven descriptor
> ---------------------------------------------
>                 Key: MJAVADOC-431
>                 URL:
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.10.3
>            Reporter: Peter lynch
>            Assignee: Michael Osipov
>             Fix For: 2.10.4
> The javadoc:jar mojo explicitly prevents the Maven descriptor from being added to the
produced javadoc.jar file.
> I could not find an explanation or technical reason why this is done.
> Adding the maven descriptor to the javadoc jar can help expose valuable information about
the build that produced it and should be at the discretion of the build process.
> Expected:
> - allow the archiver used to create the javadoc jar to respect the plexus archiver configuration
if it is configured to include the Maven descriptor.
> - preserve the default behaviour of not including the Maven descriptor, for (unknown)
backwards compatibility reasons only

This message was sent by Atlassian JIRA

View raw message