Upload Hadoop core jars to a public maven repository

• Key: HADOOP-6331
• Type: Bug
• Status: Resolved
• Resolution: Duplicate
• Priority: Major
• Assignee: Unassigned
• Reporter: Cyril Lakech

Description

There are many cool release of hadoop core and this project is an apache project, as the maven project.
But the released jars must be download manually and then deploy to a private repository before they can be used by developer using maven2.

Please could you upload the hadoop core jars on the public maven2 repository ?

Of course, we can help to deploy those artifact if necessary.

Comments

[Cyril Lakech]

Here is a sample pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>org.apache.hadoop</groupId>
<artifactId>hadoop-core</artifactId>
<version>0.20.0</version>
</project>

When you release hbase you could upload the jar and this pom to the public maven repository. For instance, the hadoop avro project seems to be uploaded on the public repo. You could contact the hadoop avro team to know how do they upload their last release (avro 1.2.0)

[Cyril Lakech]

How to upload a jar to the Apache directory ?

The public answer :
http://maven.apache.org/guides/mini/guide-central-repository-upload.html

The apache internal answer :
http://www.apache.org/dev/repository-faq.html

[Allen Wittenauer]

How does Maven deal with C code? Hadoop is not pure Java, at least, it isn't if you care about performance, the pipes API, etc, etc, ...

[Giridharan Kesavan]

With hadoop-5107 we would be able to publish hadoop jars to apache maven repo.

[Steve Loughran]

Duplicate of the HADOOP-3302 bugrep. Now that Hadoop doesn't depend on -snapshot artifacts, it is possible to push 0.21+ out through the repository

[Steve Loughran]

Allen, I don't think you could use the pure Java codebase for production servers, so we need a better way of packaging/distributing the native bits, which are tricky precisely because they aren't x-platform.

But if you are doing client side coding, or bringing up shortlived test clusters, there's no reason why the JARs you need can't go up in the repository for Ivy or Maven users to pick up. I do this in my own SCM-managed repository; I publish my builds, everyone else gets the JARs.

We could also publish some of the test libraries to the repo, benchmarks and the like, so that its easier to run them against clusters you are just bringing up.