[
https://issues.apache.org/jira/browse/HADOOP-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711171#action_12711171
]
Nigel Daley commented on HADOOP-4687:
-------------------------------------
+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:
{code}
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
{code}
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.
> Split map/reduce into sub-project
> ---------------------------------
>
> Key: HADOOP-4687
> URL: https://issues.apache.org/jira/browse/HADOOP-4687
> Project: Hadoop Core
> Issue Type: Task
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
