[
https://issues.apache.org/jira/browse/HDFS-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045631#comment-13045631
]
Owen O'Malley commented on HDFS-2045:
-------------------------------------
The HADOOP_*_HOME variables were a bad idea that I take full responsibility for.
The goal should be to move the deployment and development environments closer
together rather than have two completely different structures.
Currently, you can do:
{code}
cd common
ant rpm
rpm -i build/hadoop-common-*.rpm
cd ../hdfs
ant rpm
rpm -i build/hadoop-hdfs-*.rpm
{code}
which is far easier to understand and you are running it like it is deployed.
Of course, you can also deploy using the tarballs instead of rpm or debs.
Do you have ideas for making the dev easier? I assume part of Nigel's goal of
moving the subversion trees to gether is to eventually have a shared build
directory.
> HADOOP_*_HOME environment variables no longer work for tar ball distributions
> -----------------------------------------------------------------------------
>
> Key: HDFS-2045
> URL: https://issues.apache.org/jira/browse/HDFS-2045
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Aaron T. Myers
>
> It used to be that you could do the following:
> # Run `ant bin-package' in your hadoop-common checkout.
> # Set HADOOP_COMMON_HOME to the built directory of hadoop-common.
> # Run `ant bin-package' in your hadoop-hdfs checkout.
> # Set HADOOP_HDFS_HOME to the built directory of hadoop-hdfs.
> # Set PATH to have HADOOP_HDFS_HOME/bin and HADOOP_COMMON_HOME/bin on it.
> # Run `hdfs'.
> \\
> \\
> As of HDFS-1963, this no longer works since hdfs-config.sh is looking in
> HADOOP_COMMON_HOME/bin/ for hadoop-config.sh, but it's being placed in
> HADOOP_COMMON_HOME/libexec.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
