hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4920) do not keep forrest output in subversion
Date Mon, 22 Dec 2008 19:34:44 GMT

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

Doug Cutting updated HADOOP-4920:
---------------------------------

    Attachment: HADOOP-4920.patch

Attach patch to build documentation in build/docs/ rather than docs/.  This will not pass
Hudson, since it depends on jdiff files that are moved from docs/ to lib/.

> do not keep forrest output in subversion
> ----------------------------------------
>
>                 Key: HADOOP-4920
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4920
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Doug Cutting
>         Attachments: HADOOP-4920.patch, HADOOP-4920.sh
>
>
> We currently re-generate PDF and HTML documentation whenever we commit a 
> documentation patch, which creates huge commit messages that few read. This was 
> originally done so that folks who check out the sources from subversion did not 
> need to install forrest in order to read the documentation.
> Note, this issue only concerns the versioned documentation included in trunk and releases,
not the website, whose forrest output should continue to be kept in subversion.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message