Hadoop Map/Reduce
  1. Hadoop Map/Reduce
  2. MAPREDUCE-900

Proposed enhancements/tuning to hadoop-mapred/build.xml

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 0.21.0
    • Fix Version/s: None
    • Component/s: build
    • Labels:
      None

      Description

      sibling list of HADOOP-6206 and HDFS-560, enhancements to the mapreduce build for easier single-system build/test

        Issue Links

          Activity

          Hide
          Steve Loughran added a comment -

          if there were any changes to the build going forward, I'd use the word "gradle"

          Show
          Steve Loughran added a comment - if there were any changes to the build going forward, I'd use the word "gradle"
          Hide
          Giridharan Kesavan added a comment -

          we have done something similar in hadoop-5107

          Show
          Giridharan Kesavan added a comment - we have done something similar in hadoop-5107
          Hide
          Steve Loughran added a comment -

          Also

          1. publish hadoop-mapred-test. jar to the repositories, with its own POM file, which would aid with retrieval by hadoop-hdfs
          2. publish hadoop-mapred-examples. jar to the repositories, with its own POM file
          3. publish hadoop-mapred-tools. jar to the repositories, with its own POM file
          Show
          Steve Loughran added a comment - Also publish hadoop-mapred-test. jar to the repositories, with its own POM file, which would aid with retrieval by hadoop-hdfs publish hadoop-mapred-examples. jar to the repositories, with its own POM file publish hadoop-mapred-tools. jar to the repositories, with its own POM file
          Hide
          Steve Loughran added a comment -
          1. make project name hadoop-mapred (in lower case), so that ivy-publish publishes the artifact in that case, to aid others to pick it up
          2. ivy-report to depend on ivy-resolve, so generating the reports for every configuration
          3. replace ivy/hadoop-core.pom with ivy/hadoop-mapred.pom by rename and editing inside
          4. assert-hadoop-jar-exists target to look for {{$ {hadoop-mapred.jar}

            }}, not {{$

            {hadoop.jar}

            }}

          Show
          Steve Loughran added a comment - make project name hadoop-mapred (in lower case), so that ivy-publish publishes the artifact in that case, to aid others to pick it up ivy-report to depend on ivy-resolve, so generating the reports for every configuration replace ivy/hadoop-core.pom with ivy/hadoop-mapred.pom by rename and editing inside assert-hadoop-jar-exists target to look for {{$ {hadoop-mapred.jar} }}, not {{$ {hadoop.jar} }}

            People

            • Assignee:
              Steve Loughran
              Reporter:
              Steve Loughran
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development