hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3305) Publish hadoop-core to the apache repository with an appropriate POM file
Date Wed, 21 May 2008 22:13:56 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Steve Loughran updated HADOOP-3305:

    Attachment: ivy-support-first-pass.zip

This is a zip file containing nearly everything needed to
-pull in all the hadoop-core dependencies from Ivy
-publish the built file to a local ivy repository
-generate maven2-compatible JAR and POM, both with MD5 signatures

It doesnt make any changes to the existing build; there is a new file ivybuild.xml that lives
alongside it to do ivy work. 
ivy.xml   lists the various classpaths that get set up and their dependencies. Based on some
trial and error.
ivybuild.xml publishes the artifacts
ivy/ivysettings.xml   configuration file for ivy
ivy/libraries.properties list of all versions of all artifacts
ivy/ivy-2.0.0.rc1_20080519182948.jar (build of SVN_HEAD from monday)
ivy/hadoop-core.pom template POM file for hadoop. This is copied with property expansion to
put in correct version information, and excludes all unneeded artifacts.

I'm publishing this for people who want to integrate hadoop builds with local Ivy builds,
and to start a process of sticking hadoop artifacts up on the apache repositories. It also
shows that Ivy can be used to set up Hadoop's classpath, but doesnt make a strong case for
actually doing so
-there's no kfs.jar in the central repositories
-there's no commons-cli 2.0 artifacts in the central or snapshot repositories

What is useful for many other projects is to put the hadoop-core artifacts into the maven
repository, starting with the snapshot. That could be done using a small subset of what we
have here, though there's still the problem of no commons-cli, which the command line tools

> Publish hadoop-core to the apache repository with an appropriate POM file
> -------------------------------------------------------------------------
>                 Key: HADOOP-3305
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3305
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: build
>    Affects Versions: 0.16.2, 0.16.3
>            Reporter: Steve Loughran
>            Priority: Minor
>         Attachments: hadoop-core-0.16.2.pom, ivy-support-first-pass.zip
> 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. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message