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

Andrew Wang commented on HADOOP-8500:
-------------------------------------

So one thing to note is that the various hadoop-dist JARs are dummies, they 
don't have meaningful contents:

{noformat}
-> % jar -tf ./hadoop-dist/target/hadoop-dist-3.0.0-alpha2-SNAPSHOT.jar
META-INF/
META-INF/MANIFEST.MF
META-INF/LICENSE.txt
META-INF/NOTICE.txt
META-INF/maven/
META-INF/maven/org.apache.hadoop/
META-INF/maven/org.apache.hadoop/hadoop-dist/
META-INF/maven/org.apache.hadoop/hadoop-dist/pom.xml
META-INF/maven/org.apache.hadoop/hadoop-dist/pom.properties
{noformat}

So, I'm not sure what exactly people expect to find in this javadoc jar. 
Downstreams typically reference our hadoop-client artifact, not hadoop-dist, 
and the per-module javadocs are still being generated.

If anything, it might be a mistake that we're generating JARs in hadoop-dist at 
all. I believe the purpose of hadoop-dist is to call dist-layout-stitching to 
assemble the tarball layout from the other modules. However, since it inherits 
maven-jar-plugin from a parent pom, the default-jar execution is generating 
these dummy jars.

I'll play with a patch that cleans this up too.

> Javadoc jars contain entire target directory
> --------------------------------------------
>
>                 Key: HADOOP-8500
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8500
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 2.0.0-alpha
>         Environment: N/A
>            Reporter: EJ Ciramella
>            Assignee: Andrew Wang
>            Priority: Minor
>         Attachments: HADOOP-8500.001.patch, HADOOP-8500.patch, site-redo.tar
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The javadoc jars contain the contents of the target directory - which 
> includes classes and all sorts of binary files that it shouldn't.
> Sometimes the resulting javadoc jar is 10X bigger than it should be.
> The fix is to reconfigure maven to use "api" as it's destDir for javadoc 
> generation.
> I have a patch/diff incoming.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to