[
https://issues.apache.org/jira/browse/HADOOP-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-6629:
---------------------------------
Attachment: HADOOP-6629.patch
Here's a version of the patch that avoids log4j's dependencies by making it an
optional dependency of hadoop-common. The hadoop-mapreduce module already
directly depends on log4j so this generates a pom that works with
hadoop-mapreduce, i.e., one can use 'ant mvn-install -Dresolvers=local' and an
ivy-created pom is published such that mapreduce can be compiled and tested.
That said, I still don't get Ivy's configurations, and may have made a hash of
them.
> 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.
