Nigel Daley added a comment - 19/May/09 04:28 AM Owen, thoughts on how we should rename these jar files in the mapred and hdfs projects?
hadoop-0.21.0-dev-ant.jar
hadoop-0.21.0-dev-core.jar
hadoop-0.21.0-dev-examples.jar
hadoop-0.21.0-dev-test.jar
hadoop-0.21.0-dev-tools.jar
Giridharan Kesavan added a comment - 20/May/09 06:44 AM With this split I'm also thinking about changing the folder structure to follow maven standards. Any comments?
tnx!
I am assuming that HadoopQA will run all unit tests (both dfs and map-reduce) when a patch is submitted for the dfs sub-project (or for the map-reduce subproject).
dhruba borthakur added a comment - 20/May/09 07:04 AM I am assuming that HadoopQA will run all unit tests (both dfs and map-reduce) when a patch is submitted for the dfs sub-project (or for the map-reduce subproject).
Tom White added a comment - 20/May/09 10:25 AM As far as jar naming goes, how about
hadoop-{core,hdfs,mapred}-0.21.0-dev.jar
hadoop-{core,hdfs,mapred}-{ant,examples,test,tools}-0.21.0-dev.jar
Having the version number at the end seems to be the standard way to name things in the Ivy/Maven world.
Regarding jar names, we'll need to update bin scripts. Here are current references in the top-level bin scripts:
hadoop-config.sh:for f in $HADOOP_CORE_HOME/hadoop-*-core.jar; do
hadoop-config.sh:for f in $HADOOP_CORE_HOME/hadoop-*-tools.jar; do
hadoop-config.sh:for f in $HADOOP_CORE_HOME/build/hadoop-*-tools.jar; do
hadoop-config.sh: for f in $HADOOP_HDFS_HOME/hadoop-*-hdfs.jar; do
hdfs:for f in $HADOOP_HDFS_HOME/hadoop-*-hdfs.jar; do
mapred:for f in $HADOOP_MAPRED_HOME/hadoop-*-mapred.jar; do
rcc:for f in $HADOOP_HOME/hadoop-*-core.jar; do
Contrib bin scripts, Makefiles, etc also need to be checked and updated. Owen, this seems beyond what Giri should have to do for getting the build working. Should we file a separate Jira for that once the names are settled on.
Nigel Daley added a comment - 20/May/09 02:49 PM +1 on maven layout.
+1 on Tom's jar name suggestions.
Regarding jar names, we'll need to update bin scripts. Here are current references in the top-level bin scripts:
hadoop-config.sh:for f in $HADOOP_CORE_HOME/hadoop-*-core.jar; do
hadoop-config.sh:for f in $HADOOP_CORE_HOME/hadoop-*-tools.jar; do
hadoop-config.sh:for f in $HADOOP_CORE_HOME/build/hadoop-*-tools.jar; do
hadoop-config.sh: for f in $HADOOP_HDFS_HOME/hadoop-*-hdfs.jar; do
hdfs:for f in $HADOOP_HDFS_HOME/hadoop-*-hdfs.jar; do
mapred:for f in $HADOOP_MAPRED_HOME/hadoop-*-mapred.jar; do
rcc:for f in $HADOOP_HOME/hadoop-*-core.jar; do
Contrib bin scripts, Makefiles, etc also need to be checked and updated. Owen, this seems beyond what Giri should have to do for getting the build working. Should we file a separate Jira for that once the names are settled on.
HADOOP-4687 Merge of 776174:784663 from trunk to the branch of:
src/hdfs
src/contrib/hdfsproxy
src/test/hdfs
src/test/hdfs-with-mr
src/webapps/datanode
src/webapps/hdfs
src/webapps/secondary
HADOOP-4687 Merge of 776174:784663 from trunk to the branch, to merge:
conf/capacity-scheduler.xml.template
src/c++
src/examples
src/mapred
src/test/mapred
src/webapps/job
hadoop-0.21.0-dev-ant.jar
hadoop-0.21.0-dev-core.jar
hadoop-0.21.0-dev-examples.jar
hadoop-0.21.0-dev-test.jar
hadoop-0.21.0-dev-tools.jar