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 "Eric Yang (JIRA)" <ji...@apache.org> on 2011/06/09 18:57:59 UTC
[jira] [Created] (HADOOP-7371) Improve tarball distributions
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
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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046726#comment-13046726 ]
Alejandro Abdelnur commented on HADOOP-7371:
--------------------------------------------
Yes, we need HDFS & MR mavenized as well.
Those would be done immediately after HADOOP-6671, first HDFS and then MR.
Note that you'll be able to work on non-mavenized HDFS and MR using mavenized COMMON.
> 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
[jira] [Updated] (HADOOP-7371) Improve tarball distributions
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-7371:
--------------------------------
Fix Version/s: (was: 0.20.205.0)
0.23.0
I don't think this is a must-fix for 20.2xx.
> 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
[jira] [Updated] (HADOOP-7371) Improve tarball distributions
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HADOOP-7371) Improve tarball distributions
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Yang updated HADOOP-7371:
------------------------------
Status: Patch Available (was: Open)
> 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
>
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046687#comment-13046687 ]
Alejandro Abdelnur commented on HADOOP-7371:
--------------------------------------------
Got it, so this means this JIRA is not for trunk, right?
> 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
>
> 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
[jira] [Resolved] (HADOOP-7371) Improve tarball distributions
Posted by "Eric Yang (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Yang resolved HADOOP-7371.
-------------------------------
Resolution: Duplicate
Fix Version/s: 0.23.0
This has been resolved in Hadoop mavenization with src profile to create source tarball, and dist profile to create binary tarball.
> 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, 0.24.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.
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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Allen Wittenauer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072972#comment-13072972 ]
Allen Wittenauer commented on HADOOP-7371:
------------------------------------------
bq. Sources are compressed to a jar file as $HADOOP_PREFIX/share/hadoop/hadoop-source-[version].jar, Javadoc is compressed as $HADOOP_PREFIX/share/javadoc/hadoop-javadoc-[version].jar
Do we really want to use jar for these? This could lead to massive confusion. Besides, if these are part of the *tarball* distribution, the user clearly has *tar* available...
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047428#comment-13047428 ]
Eric Yang commented on HADOOP-7371:
-----------------------------------
Alejandro, source tarball should be the source ready to build without hadoop jar files.
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Allen Wittenauer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073662#comment-13073662 ]
Allen Wittenauer commented on HADOOP-7371:
------------------------------------------
FWIW, I'm not going to block this, but I still think it is going to lead to confusion, except for maybe the three people who debug production grids with eclipse.
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048900#comment-13048900 ]
Eric Yang commented on HADOOP-7371:
-----------------------------------
For "ant source"
- Create a hadoop-source-[version].tar.gz in build directory
> 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
>
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046713#comment-13046713 ]
Alejandro Abdelnur commented on HADOOP-7371:
--------------------------------------------
Rg Eli's comment: I'm wiring DEB/RPM in HADOOP-6671, after doing Mavenization of hadoop-common would be equivalent to Ant functionality.
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073075#comment-13073075 ]
Eric Yang commented on HADOOP-7371:
-----------------------------------
For developer, source jar files can help debugging the application in eclipse, where tar packaged source can't.
> 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
[jira] [Updated] (HADOOP-7371) Improve tarball distributions
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HADOOP-7371) Improve tarball distributions
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Yang updated HADOOP-7371:
------------------------------
Attachment: HADOOP-7371.patch
For "ant tar":
- Sources are compressed to a jar file as $HADOOP_PREFIX/share/hadoop/hadoop-source-[version].jar
- Javadoc is compressed as $HADOOP_PREFIX/share/javadoc/hadoop-javadoc-[version].jar
- Documents are relocated to $HADOOP_PREFIX/share/doc/hadoop
- HADOOP_HOME is set to be the same as HADOOP_PREFIX
> 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
>
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046686#comment-13046686 ]
Eric Yang commented on HADOOP-7371:
-----------------------------------
{quote}Because of that, wouldn't make sense to wait till Mavenization is in place for this?{quote}
Yes, for trunk, it would. For 0.20.205 branch, maven work is not going to be back ported to this branch, and it looks like a needed improvement for 0.20.205 if there is plan to make future release from 0.20-security branch.
> 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
>
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048980#comment-13048980 ]
Hadoop QA commented on HADOOP-7371:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12482496/HADOOP-7371.patch
against trunk revision 1135333.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/623//console
This message is automatically generated.
> 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
>
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047402#comment-13047402 ]
Alejandro Abdelnur commented on HADOOP-7371:
--------------------------------------------
Eric, the source TAR, should be the source ready to build, or ...?
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Allen Wittenauer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073419#comment-13073419 ]
Allen Wittenauer commented on HADOOP-7371:
------------------------------------------
Why would Eclipse users use the tarball? Besides, don't Eclipse users have other things they need to do before they can actually do things with Hadoop?
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046721#comment-13046721 ]
Eli Collins commented on HADOOP-7371:
-------------------------------------
But this jira pertains to all the projects (we release one tarball, not three), not just common. Ie we'd need the HDFS and MR side of HADOOP-6671 to use this here.
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046710#comment-13046710 ]
Eli Collins commented on HADOOP-7371:
-------------------------------------
bq. Because of that, wouldn't make sense to wait till Mavenization is in place for this?
Is common/hdfs/mr mavenization coming soon? We shouldn't block this work on a much larger project.
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073438#comment-13073438 ]
Eric Yang commented on HADOOP-7371:
-----------------------------------
Source jar + JMX + Eclipse combined can setup a debug environment when production cluster is in trouble.
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046693#comment-13046693 ]
Eric Yang commented on HADOOP-7371:
-----------------------------------
If this can be done as part of HADOOP-6671, then please change this jira to 0.20.205. Otherwise, I will submit a patch for trunk and make another jira for 0.20.205.
> 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
>
> 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
[jira] [Commented] (HADOOP-7371) Improve tarball distributions
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046678#comment-13046678 ]
Alejandro Abdelnur commented on HADOOP-7371:
--------------------------------------------
Yes, it makes senses.
As part of the Mavenization HADOOP-6671 this would be trivial.
Because of that, wouldn't make sense to wait till Mavenization is in place for this?
> 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
>
> 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