hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7371) Improve tarball distributions
Date Sun, 04 Sep 2011 02:41:10 GMT

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

Eric Yang updated HADOOP-7371:
------------------------------

    Status: Open  (was: Patch Available)

Path has became staled after mavenization.

> 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.23.0
>
>         Attachments: HADOOP-7371.patch
>
>
> 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

        

Mime
View raw message