[
https://issues.apache.org/jira/browse/HADOOP-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293031#comment-13293031
]
EJ Ciramella commented on HADOOP-8500:
--------------------------------------
That would be ideal - and truthfully - that's where I started too.
BUT - it's WAY easier to fix maven then the entire site generated around it
(forrest). That changes things from a one line fix to a touch-a-ton-of-files
fix. I was told the patch would be accepted by the community faster/easier if
it was small (for my first time).
What's sad is while exploring this fix, there are several places where the live
apache hadoop site is broken but I refrained from fixing them as well.
In fact, I was so frustrated with the site, I rewrote several of the pages in
apt, just to see how easy it'd be (I have the main site complete now).
> 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
> Priority: Minor
> Fix For: 2.0.1-alpha
>
> Attachments: HADOOP-8500.patch
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
