Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-3305

Publish hadoop-core to the apache repository with an appropriate POM file

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.16.2, 0.16.3
    • Fix Version/s: None
    • Component/s: build
    • Labels:
      None
    • Release Note:
      Hide
      This build.xml pulls the ivy.jar by itself and doesn't require any environment change except for ant-1.7.0. Builds can go as we do now expect that the machine which runs the build has to be online for resolving the dependencies as it resolves dependencies from maven repository.

      Minimum ant version requirement - 1.7.0
      Show
      This build.xml pulls the ivy.jar by itself and doesn't require any environment change except for ant-1.7.0. Builds can go as we do now expect that the machine which runs the build has to be online for resolving the dependencies as it resolves dependencies from maven repository. Minimum ant version requirement - 1.7.0

      Description

      To let people downstream build/test with hadoop, using Apache Ivy or Apache Maven2 to pull it down, hadoop-core needs to be published to the apache repository with a .pom file that lists its mandatory dependencies.

      In an automated build process, this means
      -having a template XML pom defining all included dependencies (and excluded transient dependency artifacts)
      -having a property file driving version numbering of all artifacts
      -copying this template with property expansion to create the release POM file
      -public releases only: sticking this POM file up on people.apache.org in the right place, along with the JAR and some .md5 checksums

      There's a risk that if the hadoop team dont do this, someone else will (as mahout are doing under http://people.apache.org/~kalle/mahout/maven2/org/apache/hadoop/ )
      This is bad as hadoop end up fielding the support calls from someone elses files.

      Before automating the process, existing hadoop-core JARs can be pushed out with hand-encoded POM files. The repository police dont allow pom files ever to be changed, so supporting existing releases (.16.2, 0.16.3 ... ) is a way of beta testing the POMs.

        Attachments

        1. rmlib-v3.sh
          1 kB
          Giridharan Kesavan
        2. rmlib.sh
          1 kB
          Giridharan Kesavan
        3. rmlib_V2.sh
          1.0 kB
          Giridharan Kesavan
        4. ivy-support-first-pass.zip
          849 kB
          Steve Loughran
        5. ivysupport.zip
          850 kB
          Steve Loughran
        6. ivysupport.zip
          805 kB
          Steve Loughran
        7. hadoop-core-0.16.2.pom
          4 kB
          Steve Loughran
        8. HADOOP-3305-v3.patch
          276 kB
          Giridharan Kesavan
        9. HADOOP-3305.patch
          396 kB
          Giridharan Kesavan
        10. HADOOP-3305.patch
          257 kB
          Giridharan Kesavan
        11. HADOOP-3305_V2.patch
          380 kB
          Giridharan Kesavan

        Issue Links

          Activity

            People

            • Assignee:
              gkesavan Giridharan Kesavan
              Reporter:
              stevel@apache.org Steve Loughran

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment