You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2011/06/09 19:58:01 UTC

[jira] [Updated] (HADOOP-7371) Improve tarball distributions

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

Alejandro Abdelnur updated HADOOP-7371:
---------------------------------------

    Fix Version/s: 0.20.205.0

HADOOP-6671 (in trunk) will include options to generate source/binary/tar as described in this JIRA

> Improve tarball distributions
> -----------------------------
>
>                 Key: HADOOP-7371
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7371
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>         Environment: Java 6, Redhat 5.5
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.205.0
>
>
> Hadoop release tarball contains both raw source and binary.  This leads users to use the release tarball as base for applying patches, to build custom Hadoop.  This is not the recommended method to develop hadoop because it leads to mixed development system where processed files and raw source are hard to separate.  
> To correct the problematic usage of the release tarball, the release build target should be defined as:
> "ant source" generates source release tarball.
> "ant binary" is binary release without source/javadoc jar files.
> "ant tar" is a mirror of binary release with source/javadoc jar files.
> Does this sound reasonable?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira