Adding a maven profile to disable client jar shading
Attaching initial patch
This message was automatically generated.
We can't use active by default because it would mean activating the release profile would disable running the shade plugin.
Instead, you should add a profile that sets the needed skip properties to not shade.
Rebased with trunk and incorporated Sean's suggestion. Thanks for the rev.
Shading will be suppressed using a property and invoking mvn like so:
$ mvn clean install -DskipShade -DskipTests=true
tested locally, works great!
committed to s3guard branch alongside trunk; there may be some merge issues later on, but I'll deal with that by reverting this one prior to the next merge-from-trunk
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11145 (See https://builds.apache.org/job/Hadoop-trunk-Commit/11145/)
HADOOP-13999 Add -DskipShade maven profile to disable jar shading to (stevel: rev 85e4961f60b7f8cd1343b6f2b9f4c8bb1a5de6ac)