hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paolo Castagna (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6629) versions of dependencies should be specified in a single place
Date Fri, 19 Mar 2010 16:44:31 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847432#action_12847432

Paolo Castagna commented on HADOOP-6629:

The slf4j-log4j12 v1.4.3 POM (http://repo2.maven.org/maven2/org/slf4j/slf4j-log4j12/1.4.3/slf4j-log4j12-1.4.3.pom)
does not specify a specific version of Log4J.
The POM file for Log4J v1.2.14 (http://repo2.maven.org/maven2/log4j/log4j/1.2.14/log4j-1.2.14.pom)
does not have unnecessary/broken dependencies as Log4J v1.2.15.
So, an alternative to solve issues related Log4J dependencies, could be to downgrade Log4J
version from v1.2.15 to v1.2.14... until Log4J fixes its dependencies.

Or, perhaps this isn't unnecessary, since now the Log4J dependency is correctly set to <optional>true</optional>:


As well as:


Also, if Hadoop Core has been renamed Hadoop Common, shouldn't the artifacts be consistent
and named hadoop-common-{version}[-sources,-javadocs].jar?

> 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.

View raw message