[
https://issues.apache.org/jira/browse/HADOOP-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844775#action_12844775
]
Doug Cutting commented on HADOOP-6629:
--------------------------------------
> How about mavenizing Hadoop [ ... ]
That would certainly make distributing jars to other java projects easier.
But Hadoop tends not to be used as a pure java library, but rather also
incorporates shell scripts, native code, etc. Perhaps someone familiar with
Maven can get all these to work correctly for Hadoop?
Avro's moved to a model where the primary release artifact is a tarball of the
source tree. Other derived, binary artifacts are also published: Java jars to
maven, python eggs to pypi, ruby gems, C & C++ pristine tarballs, etc. For
Hadoop, .deb and .rpm packages are useful artifacts, but I'm not sure they'd
replace the desire to also publish Maven artifacts, nor am I convinced that
Maven can build adequate .rpm or .deb packages.
So I don't yet see that Maven will satisfy all of Hadoop's build needs, but I'd
be happy to be proven wrong.
> versions of dependencies should be specified in a single place
> --------------------------------------------------------------
>
> Key: HADOOP-6629
> URL: https://issues.apache.org/jira/browse/HADOOP-6629
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Attachments: HADOOP-6629.patch, HADOOP-6629.patch
>
>
> Currently the Maven POM file is generated from a template file that includes
> the versions of all the libraries we depend on. The versions of these
> libraries are also present in ivy/libraries.properties, so that, when a
> library is updated, it must be updated in two places, which is error-prone.
> We should instead only specify library versions in a single place.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
