[HADOOP-14089] Automated checking for malformed client artifacts.

• Type: Sub-task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha2
• Fix Version/s: 3.0.0-beta1
• Target Version/s: 3.0.0-beta1
• Assignee: Sean Busbey
• Reporter: David Phillips
• Created: 16/Feb/17 18:31
• Updated: 14/Sep/17 00:15
• Resolved: 13/Sep/17 23:59

Description

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:

jar tf hadoop-client-runtime-xxx.jar | sort | grep -v '^org/apache/hadoop'

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).

Issue Links

• is related to: HBASE-18577 shaded client includes several non-relocated third party dependencies
• relates to: HADOOP-11656 Classpath isolation for downstream clients