maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MJAVADOC-431) Allow Javadoc Jar to contain Maven descriptor
Date Thu, 17 Dec 2015 22:34:46 GMT

     [ https://issues.apache.org/jira/browse/MJAVADOC-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov closed MJAVADOC-431.
-----------------------------------
    Resolution: Fixed

Fixed with [r1720689|http://svn.apache.org/r1720689].

> Allow Javadoc Jar to contain Maven descriptor
> ---------------------------------------------
>
>                 Key: MJAVADOC-431
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-431
>             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.
> https://github.com/apache/maven-plugins/blob/trunk/maven-javadoc-plugin/src/main/java/org/apache/maven/plugin/javadoc/JavadocJar.java#L299-299
> 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
(v6.3.4#6332)

Mime
View raw message