[jira] [Assigned] (MSHADE-245) Add optional parameter "createJavadocJar"

["Elliotte Rusty Harold (Jira)" <ji...@apache.org>]

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

Elliotte Rusty Harold reassigned MSHADE-245:
--------------------------------------------

    Assignee: Elliotte Rusty Harold

> Add optional parameter "createJavadocJar"
> -----------------------------------------
>
>                 Key: MSHADE-245
>                 URL: https://issues.apache.org/jira/browse/MSHADE-245
>             Project: Maven Shade Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.4.3
>            Reporter: Fabrizio Cucci
>            Assignee: Elliotte Rusty Harold
>            Priority: Major
>
> According to [this|http://central.sonatype.org/pages/requirements.html#supply-javadoc-and-sources] Sonatype OSS requirement:
> bq. Projects with packaging other than pom have to supply JAR files that contain Javadoc and sources. ... If, for some reason (for example, license issue or it's a Scala project), you can not provide -sources.jar or -javadoc.jar , please make fake -sources.jar or -javadoc.jar with simple README inside to pass the checking.
> When repackaging some dependency, it's fairly easy to create the -source.jar artifact with the maven-shade-plugin through the *createSourcesJar* optional parameter. 
> It would be nice to let the plugin also generate the -javadoc.jar through an analogous optional parameter, e.g. *createJavadocJar*.
> So far, I couldn't find an easy way to achieve the above (i.e. aggregate the javadoc of all shaded dependencies) and I've opted for the workaround suggested by the OSS requirement (i.e. fake -javadoc.jar) in order to deploy my artifact on Maven Central.
> Please find my solution [here|https://github.com/fabriziocucci/yacl4j/tree/master/yacl4j-repackaged-jackson].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)