You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2011/08/17 01:45:27 UTC
[jira] [Commented] (MAPREDUCE-2842) Maven build issues in MR2
[ https://issues.apache.org/jira/browse/MAPREDUCE-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086044#comment-13086044 ]
Arun C Murthy commented on MAPREDUCE-2842:
------------------------------------------
Alejandro - can you pls put forth a min. subset for step1 and then the rest? Tx
> Maven build issues in MR2
> --------------------------
>
> Key: MAPREDUCE-2842
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2842
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: build, mrv2
> Affects Versions: 0.23.0
> Reporter: Alejandro Abdelnur
> Labels: maven
> Fix For: 0.23.0
>
>
> * mapreduce has not been rebased on top of trunk
> * mapreduce dir/module should be named hadoop-mapreduce (following convention of common, hdfs)
> * there is lot of stuff under mapreduce that seems stale (bin/, conf, ivy/, lib/ src/)
> * yarn* dirs/modules should be named hadoop-yarn* (following convention of other Hadoop artifacts)
> * yarn/bin/ scripts should be under yarn/src/main/bin
> * yarn/conf/ scripts should be under yarn/src/main/conf
> * JAR POM files do not use hadoop-project POM as parent
> * some POM files have version parameterized and this will break things for people consuming JARs from Maven repos
> * mapreduce is not using assembly from hadoop-assemblies (the changes introduced by HDFS-2096 make the assembly/packaging reusable across different components)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira