Consider using google/jarjar instead of pantsbuild/jarjar

[cushon]

Bazel itself uses https://github.com/google/jarjar. It's actually distributed with Bazel as @bazel_tools//third_party/java/jarjar:jarjar_import, although you may not want to depend on those labels for bazel-common.

[ronshapiro]

That actually sounds good - the pantsbuild version says that it isn't meant to be used anywhere outside of pants. Fewer external dependencies to manage

…

On Thu, May 24, 2018, 6:37 PM Liam Miller-Cushon ***@***.***> wrote: Bazel itself uses https://github.com/google/jarjar. It's actually distributed with Bazel as @bazel_tools//third_party/java/jarjar:jarjar_import, although you may not want to depend on those labels for bazel-common. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#21>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAwY3eBhC_74GgCzzAgdS-424s0Lc52dks5t1zYogaJpZM4UNGk1> .

[cushon]

It's distributed with Bazel as @bazel_tools//third_party/java/jarjar:jarjar_import

Er, that's actually the pre-google/jarjar version. The next Bazel release will be using google/jarjar, but at a different label in @bazel_tools//third_party/jarjar instead.

Depending on the repo directly might be more robust than using @bazel_tools.