hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-9301) hadoop client servlet/jsp/jetty/tomcat JARs creating conflicts in Oozie & HttpFS
Date Thu, 28 Feb 2013 22:49:14 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alejandro Abdelnur updated HADOOP-9301:
---------------------------------------

    Attachment: HADOOP-9301.patch

patch cleaning up all unnecessary dependencies from hadoop-client.

Suresh, answering your question, no idea. the root problem is that hadoop and (its 3rd party
deps) do a lousy job declaring what is exactly needed. because of that, we need to curate
deps regularly, ideally we should do that as part of the release checklist.
                
> hadoop client servlet/jsp/jetty/tomcat JARs creating conflicts in Oozie & HttpFS
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-9301
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9301
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 2.0.3-alpha
>            Reporter: Roman Shaposhnik
>            Assignee: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 2.0.4-beta
>
>         Attachments: HADOOP-9301.patch
>
>
> Here's how to reproduce:
> {noformat}
> $ cd hadoop-client
> $ mvn dependency:tree | egrep 'jsp|jetty'
> [INFO] |  +- org.mortbay.jetty:jetty:jar:6.1.26.cloudera.2:compile
> [INFO] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26.cloudera.2:compile
> [INFO] |  +- javax.servlet.jsp:jsp-api:jar:2.1:compile
> {noformat}
> This has a potential for completely screwing up clients like Oozie, etc – hence a blocker.
> It seems that while common excludes those JARs, they are sneaking in via hdfs, we need
to exclude them too.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message