Details
-
New Feature
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
0.16.2, 0.16.3
-
None
-
None
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
Attachments
Issue Links
- is blocked by
-
HADOOP-3676 Remove Hadoop's dependance on the cli 2 snapshot
- Resolved
- is depended upon by
-
HADOOP-3302 Support Maven-based builds
- Closed
- is duplicated by
-
HADOOP-6331 Upload Hadoop core jars to a public maven repository
- Resolved
-
HADOOP-3817 Maven build from hadoop-core
- Closed