[
https://issues.apache.org/jira/browse/MJAVADOC-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MJAVADOC-392.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Improve generation of proper LICENSE/NOTICE for Jar
> ---------------------------------------------------
>
> Key: MJAVADOC-392
> URL: https://issues.apache.org/jira/browse/MJAVADOC-392
> Project: Maven Javadoc Plugin
> Issue Type: New Feature
> Affects Versions: 2.9.1
> Reporter: Marshall Schor
> Priority: Minor
>
> The javadoc:jar goal when run, in addition to putting into the Jar the
> generated Javadocs, also puts in all files in resource directories that end
> with "maven-shared-archive-resources". This results in the JAR having the
> same LICENSE/NOTICE files that are part of the normal JAR build.
> When the normal JAR build includes artifacts from 3rd parties (e.g., some
> icons), the normal JAR build LICENSE/NOTICE file could include parts for
> those 3rd party artifacts.
> The result of this design is that the Javadoc generated file, which doesn't
> include those 3rd party artifacts, ends up having a LICENSE/NOTICE file that
> incorrectly includes parts for those (non-present) artifacts.
> Please design a solution to mitigate this, as the LICENSE / NOTICE files
> should accurately reflect the contents of the JAR. Note that a general
> solution might need to have the ability to override the plain-vanilla
> LICENSE/NOTICE. A sample use case: suppose a Java source file being
> "javadoc'd" was a derivative of some third party artifact, and as such, had
> that 3rd party's LICENSE/NOTICE included in the normal JAR build. If the
> derivative nature bled through into the Javadoc, then (angels dancing on the
> head of a pin) the Javadoc might need the LICENSE/NOTICE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
