Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1F275EEFD for ; Sat, 2 Mar 2013 04:57:18 +0000 (UTC) Received: (qmail 46206 invoked by uid 500); 2 Mar 2013 04:57:16 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 45755 invoked by uid 500); 2 Mar 2013 04:57:15 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 45698 invoked by uid 99); 2 Mar 2013 04:57:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Mar 2013 04:57:13 +0000 Date: Sat, 2 Mar 2013 04:57:13 +0000 (UTC) From: "Alejandro Abdelnur (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-9301) hadoop client servlet/jsp/jetty/tomcat JARs creating conflicts in Oozie & HttpFS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-9301?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D135= 91297#comment-13591297 ]=20 Alejandro Abdelnur commented on HADOOP-9301: -------------------------------------------- The patch I'm working on (more on that after in the next paragraph) disable= s 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 r= esulting hadoop-client JARs in Oozie) but I'm running into other issues bet= ween Hadoop trunk and Oozie 3.3.1, thus have to diagnose that too. =20 > 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 = =E2=80=93 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 administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira