incubator-hcatalog-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HCATALOG-184) Optionally do not generate forrest docs
Date Wed, 21 Dec 2011 18:23:30 GMT

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

Ashutosh Chauhan commented on HCATALOG-184:
-------------------------------------------

Its a dev who builds the most and its his experience that we want to optimize. So, I think
default option is to have forrest off by default. At the time of release or when someone is
interested they can generate forrest by passing -Dforrest=true. What do you think?
                
> Optionally do not generate forrest docs
> ---------------------------------------
>
>                 Key: HCATALOG-184
>                 URL: https://issues.apache.org/jira/browse/HCATALOG-184
>             Project: HCatalog
>          Issue Type: Bug
>            Reporter: Travis Crawford
>         Attachments: HCATALOG-184.diff
>
>
> Currently {{ant package}} requires generating Forrest docs, which in general is a good
thing. However, this is problematic on private networks for two reasons:
> # Forrest may not be available on build machines. This can be worked around by checking
in a forrest release (either the extracted sources, or extract the release on demand) as part
of your build process. However, docs are not strictly required and in practice no one will
look at the docs on a production machine.
> # Forrest expects a public internet connection. Forrest attempts to update its plugins
from a public internet location, which causes the HCatalog build to fail.
> For these reasons, I propose adding a {{-Dnoforrest}} ant property that disables building
the forrest documentation. By default, it still builds the docs so most users will not notice.
However, users attempting to build on a private network will not have to patch around doc
generation.

--
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

        

Mime
View raw message