hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7952) simplify common back to a single jar
Date Wed, 04 Jan 2012 23:07:39 GMT

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

Alejandro Abdelnur commented on HADOOP-7952:

We don't need to  carry this to its logical conclusion. I don't think we have any other part
of common that is used outside of hadoop in the same why as auth is.

Yes, oozie-client could use common JAR and block all dependencies that are not needed. However
this has 2 problems, you have to be aware of which dependencies are needed for auth and when
common adds a new dependency oozie-client will have to filter that out. In other words, you
lose the dependency management.

What is your proposal for extra/auth? (I may have missed that)
> simplify common back to a single jar
> ------------------------------------
>                 Key: HADOOP-7952
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7952
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
> The current build is too complex and we should move to a simple project for common.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message