Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 16 Feb 2017 18:31:41 +0000 (UTC)
From: "David Phillips (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13043710.1487269893000.102093.1487269901953@Atlassian.JIRA>
In-Reply-To: <JIRA.13043710.1487269893000@Atlassian.JIRA>
References: <JIRA.13043710.1487269893000@Atlassian.JIRA> <JIRA.13043710.1487269893328@jira-lw-us.apache.org>
Subject: [jira] [Created] (HADOOP-14089) Shaded Hadoop client runtime
 includes non-shaded classes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 16 Feb 2017 18:31:48 -0000

David Phillips created HADOOP-14089:
---------------------------------------

             Summary: Shaded Hadoop client runtime includes non-shaded classes
                 Key: HADOOP-14089
                 URL: https://issues.apache.org/jira/browse/HADOOP-14089
             Project: Hadoop Common
          Issue Type: Bug
    Affects Versions: 3.0.0-alpha2
            Reporter: David Phillips


The jar includes things like {{assets}}, {{okio}}, {{javax/annotation}}, {{javax/ws}}, {{mozilla}}, etc.

An easy way to verify this is to look at the contents of the jar:
{code}
jar tf hadoop-client-runtime-xxx.jar | sort | grep -v '^org/apache/hadoop'
{code}

For standard dependencies, such as the JSR 305 {{javax.annotation}} or JAX-RS {{javax.ws}}, it makes sense for those to be normal dependencies in the POM -- they are standard, so version conflicts shouldn't be a problem. The JSR 305 annotations can be {{<optional>true</optional>}} since they aren't needed at runtime (this is what Guava does).


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org