hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8916) make it possible to build hadoop tarballs without java5+ forrest
Date Sun, 14 Jul 2013 11:56:48 GMT

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

Harsh J commented on HADOOP-8916:

- Forrest is required as a normal release tarball build dependency. To skip it could make
release builds unintuitive, and we may end up producing releases without docs properly compiled
in it. Currently we're immediately notified we did not pass it.
- JDK5 is no longer required. This is already done via other JIRA. If we still need this to
go in, please change the JIRA summary appropriately.
- The chinese docs, cn-docs, is not a default target for anything else anymore, as it is currently
unmaintained. But to remove forrest.check from it would mean if one were to try to build it
directly, it wouldn't work unless forrest.home is auto-specified (as no check is performed).
This could get unintuitive.
> make it possible to build hadoop tarballs without java5+ forrest
> ----------------------------------------------------------------
>                 Key: HADOOP-8916
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8916
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 1.0.3, 1.3.0
>            Reporter: Steve Loughran
>            Priority: Trivial
>         Attachments: HADOOP-8916.patch
>   Original Estimate: 1m
>  Remaining Estimate: 1m
> Although you can build hadoop binaries without java5 & Forrest, you can't do the
tarballs as {{tar}} depends on {{packaged}}, which depends on the {{docs}} and {{cn-docs}},
which both depend on the forrest/java5 checks. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message