[HBASE-13517] Publish a client artifact with shaded dependencies

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0, 2.0.0
• Fix Version/s: 1.1.0, 2.0.0
• Hadoop Flags: Reviewed

Release Note

HBase now provides added convenience artifacts that shade most dependencies. These jars hbase-shaded-client and hbase-shaded-server are meant to be used when dependency conflicts can not be solved any other way. The normal jars hbase-client and hbase-server should still be preferred when possible.

Do not use hbase-shaded-server or hbase-shaded-client inside of a co-processor as bad things will happen.

• Assignee: Elliott Neil Clark
• Reporter: Elliott Neil Clark
• Created: 21/Apr/15 00:28
• Updated: 12/Aug/17 06:57
• Resolved: 28/Apr/15 16:50

Description

Guava's moved on. Hadoop has not.
Jackson moves whenever it feels like it.
Protobuf moves with breaking point changes.

While shading all of the time would break people that require the transitive dependencies for MR or other things. Lets provide an artifact with our dependencies shaded. Then users can have the choice to use the shaded version or the non-shaded version.

Issue Links

• relates to: HBASE-18577 shaded client includes several non-relocated third party dependencies