[
https://issues.apache.org/jira/browse/HADOOP-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591297#comment-13591297
]
Alejandro Abdelnur commented on HADOOP-9301:
--------------------------------------------
The patch I'm working on (more on that after in the next paragraph) disables
transitive dependencies that are not required, we have to do that one by one
when we verify that they are not needed on the client side.
I've spent a good chunk of the day trying to validate my patch (using the
resulting hadoop-client JARs in Oozie) but I'm running into other issues
between Hadoop trunk and Oozie 3.3.1, thus have to diagnose that too.
> 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
