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 Tue, 25 Nov 2008 16:19:44 GMT

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

Steve Loughran updated HADOOP-3305:
-----------------------------------

    Attachment: ivysupport.zip

This is what I'm working on right now; it publishes the core hadoop artifacts to the local
repository, where my other build can grab them. I also take the new artifacts and stick them
in an SVN-managed repository so that our hudson build runs against the releases I make, with
some work needed to make sure that my local build doesn't pick up those (usually dated) artifacts,
but instead stays up to date with whatever I build. 

The versions I have for things are

commons-cli.version=2.0-SNAPSHOT
commons-codec.version=1.3
commons-httpclient.version=3.0.1
commons-net.version=1.4.1
commons-logging.version=1.0.4
commons-el.version=1.0
hsqldb.version=1.8.0.7
ivy.version=2.0.0.rc1_20080519182948
jasper.version=5.5.12
jsp-api.version=${jasper.version}
jets3t.version=0.6.0
jetty5.version=5.1.4
junit.version=3.8.1
kfs.version=0.1
log4j.version=1.2.15
oro.version=2.0.8
servletapi.version=2.4
xmlenc.version=0.52

This hasn't migrated to jetty6 yet, and it used an early release of Ivy; it should work with
the latest official release now. 

commons-cli versions is a problem -there hasn't been an official release there for a while.
The solution there is to persuade them to release one.
json is a different problem in that there isn't an official release at all; you get to build
your own, and often they have different MD5 checksums just from manifest.mf metadata. We need
a better idea of what they built against and maybe stick something unofficial in the repository
that works.

> 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-3305.patch, hadoop-core-0.16.2.pom, ivy-support-first-pass.zip,
ivysupport.zip, rmlib.sh
>
>
> 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.


Mime
View raw message